Fix issue
Custom configuration for Claude Code that turns it into a disciplined engineering partner with structured workflows, strict guardrails, and domain-specific expertise.
npx -y skills add domengabrovsek/claude --skill fix-issueAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Investigate and fix a GitHub issue. Use when given an issue number or URL, or when the user says 'fix issue'.
SKILL.md
2.1 KB, as published. Nobody here has run it
Fix the GitHub issue: $ARGUMENTS
Follow this workflow:
why-not-mechanizable: 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,commentsto get full issue details(review-time: see section note) - Load agents: based on the issue domain, load the relevant expert agents from
~/.claude/agents/(seerules/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>.mdwith:(review-time: see section note)- Root cause analysis
- Files to change (with specific line ranges)
- Risks and edge cases
- Wait for user approval before implementing
- Implement: make the changes following the approved 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: push the branch and create a PR linking the issue with
gh pr create(hook)