Menu
Fix a GitHub issue end-to-end. Use when given an issue number to fix, implementing bug fixes, or addressing reported problems.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Build the project and automatically fix any build errors, compilation failures, or type mismatches. Use when the project fails to build, shows "broken" states, or after making significant changes.
Perform a "hard reset" of the development environment. Use when dependencies are corrupted, lockfiles are out of sync, or environment tools (Trunk/uv) are in an inconsistent state.
Self-improvement skill for evolving Claude Code configuration. Use when you notice repeated mistakes, want to add new workflows, or optimize the development experience. Enables Claude to improve its own CLAUDE.md, skills, hooks, and agents.
Run linters and fix violations, formatting errors, or style mismatches using Trunk. Use when code quality checks fail, before submitting PRs, or to repair "broken" linting states.
Manage Architecture Decision Records (ADRs) using adr-tools. Use this to initialize, create, list, and link ADRs to document architectural evolution.
Manage changelogs using Changie. Provides tools to initialize, add change fragments, batch releases, and merge version notes.
| name | fix-issue |
| description | Fix a GitHub issue end-to-end. Use when given an issue number to fix, implementing bug fixes, or addressing reported problems. |
A complete workflow for fixing GitHub issues from understanding the problem to creating a pull request.
$ARGUMENTS: GitHub issue number (e.g., 123 or #123)gh issue view $ARGUMENTS
Analyze:
Search for relevant code:
# Search for keywords from the issue
grep -r "keyword" src/
# Find related files
find . -name "*.py" | xargs grep -l "related_term"
Understand:
git checkout -b fix/issue-$ARGUMENTS-<brief-description>
Apply the minimum necessary change to resolve the issue:
Create tests that:
Run the verification cycle:
make lint
make test
make build
Or invoke the verifier subagent for comprehensive validation.
git add <specific-files>
git commit -m "fix(scope): brief description
Fixes #$ARGUMENTS"
git push -u origin fix/issue-$ARGUMENTS-<brief-description>
gh pr create --title "fix(scope): description" --body "$(cat <<'EOF'
## Summary
Fixes #$ARGUMENTS
## Problem
[Description of the issue]
## Solution
[How this PR fixes it]
## Testing
- [ ] Added test case for the bug
- [ ] All tests pass
- [ ] Manually verified the fix
## Changes
- [List specific changes]
EOF
)"
Input: /fix-issue 42
Workflow:
gh issue view 42 - User reports "import fails with ModuleNotFoundError"git checkout -b fix/issue-42-import-errorsrc/your_package/__init__.pytest_import_module.pymake lint && make testgit commit -m "fix(imports): resolve ModuleNotFoundError\n\nFixes #42"| Task | Command |
|---|---|
| View issue | gh issue view <number> |
| List issues | gh issue list |
| Create branch | git checkout -b fix/issue-<n>-<desc> |
| Link PR to issue | Include Fixes #<n> in commit message |
| Close issue via PR | Include Closes #<n> in PR body |