fix-issue · frappe — Claude Code skill: fix bugs from GitHub issues
fix-issue turns a bug report into a fix: a subagent extracts the facts, the main agent reproduces the bug and traces the cause without inheriting the reporter's guesses.
no license 431 installs ★ 177 updated 2026-10-24
npx skills add frappe/skills --skill fix-issue -a claude-codeWhat fix-issue does
The skill takes an issue number, a link to the issue, or a path to a markdown file. A general-purpose subagent reads the report and returns a factual brief: symptom, expected result, reproduction steps, error text, environment, scope. Proposed patches, hunches about the cause and comments like "the bug is in x.py" never reach the main context. The main agent does not open the report itself, not even to check one detail later; it asks the same extractor through SendMessage.
Reproduction comes before any edit. Three results end the run early: the bug does not reproduce and the brief lists gaps, it does not reproduce while the brief is complete, or it reproduces but the behaviour is correct. When the bug is confirmed, the cause gets traced through the code and the fix stays minimal, with a regression test that fails without it, the surrounding test module and pre-commit run --files <changed files>.
Reading a GitHub issue needs gh on the machine, because the extractor calls gh issue view <n> --comments. The diff goes to a second agent that loads the frappe-code-review skill, so that skill is required for the review step.
What it helps with
- turn a noisy GitHub issue into a factual brief
- reproduce a reported bug before touching code
- trace the defect through the code, not through the reporter's hints
- add a regression test that fails without the fix
- hand the working diff to a second agent for review
Example prompts for the agent
- Use the fix-issue skill on issue 4210 and fix the bug
- Reproduce the bug in
docs/bugs/login.mdand trace the cause - Fix the reported issue, then have a separate agent review the diff
How to install fix-issue
1Skills CLI (Vercel)
npx skills add frappe/skills --skill fix-issue -a claude-code2Manually: put the files in place
~/.claude/skills/fix-issue/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/fix-issue/
1Skills CLI (Vercel)
npx skills add frappe/skills --skill fix-issue -a codex2Manually: put the files in place
.agents/skills/fix-issue/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add frappe/skills --skill fix-issue -a cursor2Manually: put the files in place
.cursor/skills/fix-issue/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install frappe/skills skills/fix-issue2Manually: put the files in place
.github/skills/fix-issue/SKILL.md1Skills CLI (Vercel)
npx skills add frappe/skills --skill fix-issue -a gemini-cli2Platform CLI
gemini skills install https://github.com/frappe/skills --path skills/fix-issueManually: put the files in place
.devin/skills/fix-issue/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add frappe/skills --skill fix-issue -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about fix-issue
How to install fix-issue in Claude Code?
Run npx skills add frappe/skills --skill fix-issue -a claude-code. The skill lands at ~/.claude/skills/fix-issue/SKILL.md.
What does fix-issue do?
It sends a subagent to pull facts out of a bug report, then reproduces the bug, traces the cause, applies a minimal fix with a regression test and passes the diff to a reviewer agent.
Why doesn't the main agent read the issue itself?
Guesses in the report steer the search and make the symptom look like the cause. The extractor keeps only what can be observed, and the main agent builds its own theory from the code.
Similar skills
All skills for Agent setup: memory, context, orchestration →fix-issue by other authors comes first.