| name | fix-issue |
|---|---|
| description | Read a GitHub issue, implement the fix, write tests, and commit. |
| argument-hint | <issue-number> |
| allowed-tools | Bash, Read, Grep, Glob |
Fix GitHub issue #$ARGUMENTS.
Follow these steps:
-
Fetch the issue details with
gh issue view $ARGUMENTS. Read the title, body, and any comments carefully. -
Explore the codebase to find the relevant code:
- Search for symbols, file names, or error messages mentioned in the issue.
- Read the affected files to understand the current behavior.
-
Plan the fix. Write a short plan (3-5 bullet points) before making any changes. Include:
- Root cause of the issue.
- Files that need to change.
- How the fix addresses the root cause without introducing regressions.
-
Implement the fix. Make minimal, focused changes. Do not refactor unrelated code.
-
Write or update tests that:
- Reproduce the bug (a test that would have caught this issue before the fix).
- Verify the fixed behavior. Place tests in the appropriate test file following the project's existing conventions.
-
Run the test suite to confirm all tests pass (including pre-existing tests).
-
Stage the changed files and commit with a message in this format:
fix: <short description> (closes #$ARGUMENTS)Include a brief body explaining the root cause and the approach taken. -
Summarize what was changed and why.