fix-issue · git:20261116.18a1a15 · 2026-11-16 · sha256 a778f009c6f24ff7

fix-issue git:20261116.18a1a15A

Immutable. This exact content never changes and is served at /api/v1/blob/a778f009c6f24ff7.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_46xn4she7mo2y4ai/a778f009c6f24ff7566d26af40650bf95a58e4f3d5688c9d2394100afd5becb9.json

Then /plugin install fix-issue@markdownregistry-46xn4she7mo2y4ai in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: fix-issue
description: "Investigates and fixes a GitHub issue. Use when given an issue number or URL, or when the user says 'fix issue'."
---

Fix the GitHub issue: $ARGUMENTS

Resolve `$STATE` first: `.claude/state` in the main checkout of the repo being changed, per `rules/state-persistence.md`.

Follow this workflow:

**why-no-hook:** skill workflow guidance; each step requires understanding the issue, the codebase, and the prior state of the work.

1. **Fetch**: run `gh issue view $ARGUMENTS --json title,body,labels,assignees,comments` to get full issue details `(review-time: see section note)`
2. **Check prior work**: run `gh pr list --state open --search "<issue number>"` in the issue's repo and read the comments for a claim. An open PR or claim exists? Stop and ask the user before writing code `(review-time: see section note)`
3. **Spawn experts**: based on the issue domain, spawn the matching expert teammates (see `rules/agent-routing.md`). Their guardrails apply throughout the fix. `(review-time: see section note)`
4. **Research**: use subagents to explore the codebase and understand the problem area. Read linked files, related tests, and recent git history. Save findings to `$STATE/research/YYYY-MM-DD-issue-<number>.md`. `(review-time: see section note)`
5. **Reproduce**: if possible, write a failing test that reproduces the issue `(review-time: see section note)`
6. **Scope check**: before planning the fix, state the minimal change that would resolve the issue (ideally 1-5 lines). If a larger change is needed, explain why the minimal fix is insufficient. The plan must build from this minimal baseline. `(review-time: see section note)`
7. **Plan**: propose a fix plan and save to `$STATE/plans/YYYY-MM-DD-fix-issue-<number>.md` with: `(review-time: see section note)`
   - Root cause analysis
   - Files to change (with specific line ranges)
   - Risks and edge cases
   - Continue without asking unless the plan needs an architectural choice the issue leaves open
8. **Implement**: make the changes following the plan `(review-time: see section note)`
9. **Test**: write or update tests verifying the fix. Run the test suite. `(review-time: see section note)`
10. **Verify**: run `npm run verify:fast` when package.json declares it. Otherwise run the typecheck (`npx tsc --noEmit`), lint, and full test suite. `/mr` runs the full gate once `(hook)`
11. **Commit**: create a conventional commit (e.g., `fix(scope): description`) referencing the issue `(hook)`
12. **PR**: create the PR with `/mr`, which pushes the branch. Put `Closes #<issue>` under Linked issues `(hook)`