Installs into .claude/skills of the current project.
Are you the author of Fix Issue?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/domengabrovsek-fix-issue)
---
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
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. **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)`
3. **Research**: use subagents to explore the codebase and understand the problem area. Read linked files, related tests, and recent git history. Save findings to `.claude/state/research/YYYY-MM-DD-issue-<number>.md`. `(review-time: see section note)`
4. **Reproduce**: if possible, write a failing test that reproduces the issue `(review-time: see section note)`
5. **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)`
6. **Plan**: propose a fix plan and save to `.claude/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
7. **Implement**: make the changes following the plan `(review-time: see section note)`
8. **Test**: write or update tests verifying the fix. Run the test suite. `(review-time: see section note)`
9. **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)`
10. **Commit**: create a conventional commit (e.g., `fix(scope): description`) referencing the issue `(hook)`
11. **PR**: create the PR with `/mr`, which pushes the branch. Put `Closes #<issue>` under Linked issues `(hook)`
