Claude Skill

fix-issue

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

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download domengabrovsek-claude-skills_fix-issue-48da5d0.zip · 1 KB

domengabrovsek/claude 17 4 forks Updated 2d ago

Part of domengabrovsek/claude — 41 skills

Install

skills CLI npx skills add https://github.com/domengabrovsek/agent-config/tree/main/skills/fix-issue

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install domengabrovsek-claude@llmmart

Git git clone https://github.com/domengabrovsek/agent-config.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole domengabrovsek/claude collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.

Fetch: run gh issue view $ARGUMENTS --json title,body,labels,assignees,comments to get full issue details (review-time: see section note)
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)
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)
Reproduce: if possible, write a failing test that reproduces the issue (review-time: see section note)
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)
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
Implement: make the changes following the plan (review-time: see section note)
Test: write or update tests verifying the fix. Run the test suite. (review-time: see section note)
Verify: run typecheck (npx tsc --noEmit), lint, and full test suite (hook)
Commit: create a conventional commit (e.g., fix(scope): description) referencing the issue (hook)
PR: create the PR with /mr, which pushes the branch. Put Closes #<issue> under Linked issues (hook)

Files (claude)

SKILL.md 2.1 KB

---
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 typecheck (`npx tsc --noEmit`), lint, and full test suite `(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)`