Fix Issue
Resolve a GitHub issue end to end, from reading the issue through to opening a pull request. Use when the user names an issue number to fix.
Install
/plugin marketplace add smartwhale8/claude-playbookThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add smartwhale8/claude-playbook --skill fix-issuegit clone --depth 1 https://github.com/smartwhale8/claude-playbook.git /tmp/claude-playbook
mkdir -p ~/.claude/skills
cp -r /tmp/claude-playbook/.claude/skills/fix-issue ~/.claude/skills/fix-issuePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Fix issue $ARGUMENTS ## The issue !`gh issue view $ARGUMENTS 2>&1 || echo "Could not read issue $ARGUMENTS. Check the number and that gh is authenticated."` ## Workflow 1. **Understand.** Read the issue above. If the expected behaviour is ambiguous, ask before writing code. A wrong fix costs more than a question. 2. **Reproduce.** Find the failing behaviour in the code. Do not proceed on a theory you have not confirmed. 3. **Plan.** State the root cause and the change you intend, before editing. If the cause is unclear, say so instead of guessing. 4. **Branch.** `git switch -c fix/<short-description>`. Never commit to the default branch. 5. **Test first.** Write a test that fails because of this bug. Run it and watch it fail. A regression test that never failed proves nothing. 6. **Fix.** Address the cause. If the fix spans several files, explain why in the pull request. 7. **Verify.** Run the new test, then the full suite, then lint and type checks. Paste what the commands returned. Never assert success without the output. 8. **Commit and open the pull request.** Reference the issue. The description covers what changed, why, how it was verified, and any risk. ## Rules - The root cause, never the symptom. If the first idea is a workaround, keep looking. - Do not change anything the issue did not ask for. - If the fix turns out to need a decision that is not yours to make, stop and report what you found.
Details
- Skill name
fix-issue- Repository
- smartwhale8/claude-playbook
- Path
.claude/skills/fix-issue/SKILL.md- License
- MIT
- Repo updated
- 20 September 2026
FAQ
What does the Fix Issue skill do?
Resolve a GitHub issue end to end, from reading the issue through to opening a pull request. Use when the user names an issue number to fix.
How do I install the Fix Issue skill?
Claude Code plugin: /plugin marketplace add smartwhale8/claude-playbook. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Fix Issue popular?
It lives in smartwhale8/claude-playbook, which has 44 GitHub stars and 5 forks.
Related skills
Plan Feature
44smartwhale8/claude-playbook
Turn a rough feature idea into a written specification by interviewing the user first. Use when the user describes something substantial they want built and the approach is not yet settled.
Review
44smartwhale8/claude-playbook
Review uncommitted changes against the project rules before committing. Use when the user asks for a review of their working tree, asks whether changes are ready to commit, or says they are about to commit.
Review PR
44smartwhale8/claude-playbook
Review a pull request for correctness, architecture, security, and test coverage. Use when the user names a PR number to review.
Weekly Changelog
49hw-native-sys/simpler
Summarize user-facing changes merged in the current Friday-anchored week (most recent Friday up through yesterday) in the simpler repo into a markdown changelog with before/after code examples. Also emits a full all-PR inventory (WEEKLY_ALL_PRS) and Chinese (_zh) translations of both docs. Use when the user asks for a weekly changelog, weekly summary, or weekly external changes report.
Regel Check
51neubauerwilli/gta6-skill
Der Regel-Check. Prüft jeden Clip gegen die Regeln der Kampagne (Länge, Wasserzeichen, Pflicht-Tags, Erwähnung, Plattform, Frist), bevor er rausgeht. Nutze ihn immer vor dem Posten, oder wenn der Nutzer sagt "prüf den Clip", "darf ich das posten", "Regeln checken" oder "ist der Clip okay".
Vicious Mockery
113Hmbown/Wizards-of-the-Ghosts
The bard's cantrip that deals psychic damage through insults. In practice this is adversarial review — the art of finding and articulating exactly what is wrong with something in a way that is impossible to ignore. Unlike polite feedback that gets filed and forgotten, vicious mockery lands. It is the red-team report that makes the PM cancel the launch, the code review that makes the author delete the PR, the roast that makes the founder pivot. The damage is the point.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.