// Fix a GitHub issue end-to-end - from reading the issue, understanding requirements, implementing the fix, writing tests, and creating a commit. Use when given a GitHub issue number or URL to resolve.
Automatic quality control, linting, and static analysis procedures. Use when validating code changes for syntax correctness and project standards. Triggers on keywords: lint, format, check, validate, types, static analysis.
Refactoring and cleanup - improving code structure, removing dead code, eliminating duplication, or pre-merge cleanup. Use when code is hard to maintain, has dead code or debug artifacts, or needs pre-merge polishing.
Optimize code for readability, performance, maintainability, and security across Bash, Python, and Rust. Use when asked to improve code quality, optimize performance, add type safety, or refactor for idioms.
Create, debug, and optimize GitHub Actions workflows with security best practices. Use when asked to "create workflow", "fix workflow", "add CI", or needs help with GitHub Actions.
Review code changes (diffs, PRs, patches) and provide structured, actionable feedback on correctness, maintainability, and test coverage. Use when the user asks for a code review, requests feedback on a patch/PR, or wants an assessment of changes.
Craft immersive, high-performance premium web experiences with advanced motion, typography, and architectural craftsmanship. Use when building award-level landing pages, interactive portfolios, or components requiring top-tier visual polish.
| name | fix-issue |
| description | Fix a GitHub issue end-to-end - from reading the issue, understanding requirements, implementing the fix, writing tests, and creating a commit. Use when given a GitHub issue number or URL to resolve. |
| allowed-tools | Bash(git:*), Bash(gh:*), Bash(npm:*), Bash(npx:*), Bash(uv:*), Bash(pytest:*), Bash(ruff:*), Read, Write, Edit, Glob, Grep |
Resolve GitHub issue $ARGUMENTS following repository coding standards.
Think step-by-step through the issue resolution:
Read the issue: Fetch issue details with gh issue view $ARGUMENTS
Understand scope: Before writing code, determine:
Implement the fix:
git checkout -b fix/issue-$ARGUMENTSinstructions/ files for language-specific standardsWrite or update tests:
Verify:
Commit and document:
git add -Agit commit -m "fix: <description> (#$ARGUMENTS)"Closes #$ARGUMENTS in the commit body if appropriateInput: fix-issue 42
Steps:
1. gh issue view 42 -> "Login button unresponsive on mobile"
2. Search: rg "login" src/components/ -> LoginButton.tsx
3. Root cause: click handler missing touch event
4. Fix: add onTouchEnd handler alongside onClick
5. Test: add mobile viewport test
6. git commit -m "fix: add touch event to login button (#42)"
Input: fix-issue 87
Steps:
1. gh issue view 87 -> "Add dark mode toggle to settings"
2. Search: rg "theme" src/ -> ThemeProvider.tsx, settings.tsx
3. Implement: add toggle component using existing ThemeProvider
4. Test: verify toggle switches theme, persists preference
5. git commit -m "feat: add dark mode toggle to settings (#87)"