Skip to content
Agentmart
Submit a tool

codepilot-be

Backend feature-development router.

Skill by galorr

IndexedMIT
Write a review

Install

Works with Claude Code. Read the repository before you give any tool access to your data.

npx agentmarket install skill/galorr-codepilot-be

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Backend feature-development router. Detects the backend framework (NestJS, Next.js, or Python) from the repo and Jira ticket, then dispatches to the matching per-language skill (codepilot-be-nestjs / codepilot-be-nextjs / codepilot-be-python). Falls back to a generic flow for anything else. Use when the user provides a Jira ticket link and wants the full backend development loop handled autonomously. Trigger on "implement this backend ticket", "build this API story", "start on this backend task", or when a Jira URL is pasted with backend/API context.

Use cases: frontend, backend, productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/codepilot-be

Tools it pre-approves 12

From allowed-tools in SKILL.md: the agent may use these without asking you each time.

  • Bash,
  • Read,
  • Edit,
  • Write,
  • Glob,
  • Grep,
  • Skill,
  • mcp__atlassian__getJiraIssue,
  • mcp__atlassian__editJiraIssue,
  • mcp__atlassian__addCommentToJiraIssue,
  • mcp__atlassian__getTransitionsForJiraIssue,
  • mcp__atlassian__transitionJiraIssue

What's inside

Skill name
codepilot-be
Description
Backend feature-development router. Detects the backend framework (NestJS, Next.js, or Python) from the repo and Jira ticket, then dispatches to the matching per-language skill (codepilot-be-nestjs / codepilot-be-nextjs / codepilot-be-python). Falls back to a generic flow for anything else. Use when the user provides a Jira ticket link and wants the full backend development loop handled autonomously. Trigger on "implement this backend ticket", "build this API story", "start on this backend task", or when a Jira URL is pasted with backend/API context.
License
MIT
Allowed tools
Bash,, Read,, Edit,, Write,, Glob,, Grep,, Skill,, mcp__atlassian__getJiraIssue,, mcp__atlassian__editJiraIssue,, mcp__atlassian__addCommentToJiraIssue,, mcp__atlassian__getTransitionsForJiraIssue,, mcp__atlassian__transitionJiraIssue
Instructions
49 lines in SKILL.md · view on GitHub

Before installing

  • Pre-approves some shell commands

Files (1)

  • SKILL.md

SKILL.md (first lines)

# CodePilot BE — Backend Framework Router

Detects the backend framework, then hands off to the matching per-language skill.
Each language skill owns the framework-specific development loop; the shared
orchestration (ticket, branch, commit, CR) lives in
`skills/_shared/references/codepilot-common.md`.

## Required Inputs
- Jira ticket URL
- (Optional) User availability: `available` | `unavailable`

## Step 1: Fetch the ticket

Retrieve the ticket (Shared Phase A of `codepilot-common.md`) so its labels and
`relatedServices[]` can feed detection. Do **not** transition it yet — the
dispatched skill will run the full shared flow including the In Progress transition.

## Step 2: Detect the backend framework

Follow `skills/_shared/references/framework-detection.md`. Inspect the repo first
(package.json, `nest-cli.json`, `next.config.*`, `pyproject.toml` / `requirements.txt`)
and use ticket labels as a tie-breaker. Only ask the user when signals are missing
or conflicting.

Store the result as `beFramework`.

## Step 3: Dispatch

| `beFramework` | Invoke skill |
|---------------|--------------|
| `NestJS` | `codepilot-be-nestjs` |
| `Next.js` | `codepilot-be-nextjs` |
| `Python` | `codepilot-be-python` |
| _anything else / undetected_ | **default** — run `## Default / Generic Flow` in `codepilot-common.md` |

Use the `Skill` tool to invoke the chosen skill, forwarding the ticket URL and all
original arguments. Inform the user which framework was detected and which skill is
taking over, e.g.:
> Detected backend framework: **NestJS** → handing off to `codepilot-be-nestjs`.

For the default path, warn per the generic-flow instructions and proceed — never stop.

## Key Rules
- Always detect before dispatching; inspect the repo, ask only when unclear.
- Forward the ticket URL and arguments unchanged to the dispatched skill.
- Never run two language skills for one ticket — pick one.
- For unsupported/undetected stacks, run the default generic flow with a clear warning; do not stop.

From galorr/claude-code-starter, MIT.

More from galorr/claude-code-starter

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Jul 14, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from galorr

Cite this page

codepilot-be skill. Agent Mart. https://agentmart.dev/skills/galorr-codepilot-be (last updated 2026-10-24)