Claude Code · Slash command
/fix-github-issue
Give it an issue number — it reads the issue via `gh`, finds the relevant code, fixes it, tests it, and commits.
708★ · from Kotlinter, a widely-used Kotlin linter Gradle plugin
What this actually does for you
You paste in an issue number instead of an explanation. It reads the actual GitHub issue itself, works out what's broken, fixes it, tests it, and writes the commit — you don't have to re-explain the bug in your own words at all.
Try it for: Work through a whole backlog of small, well-described bugs this way — one `/fix-github-issue 142`, `/fix-github-issue 143`... per issue — and clear a sprint's worth of minor tickets in an afternoon instead of a week.
The command file
Please analyze and fix the GitHub issue: $ARGUMENTS.
Follow these steps:
1. Use `gh issue view` to get the issue details
2. Understand the problem described in the issue
3. Search the codebase for relevant files
4. Implement the necessary changes to fix the issue
5. Write and run tests to verify the fix
6. Ensure code passes linting and type checking
7. Create a descriptive commit message
Remember to use the GitHub CLI (`gh`) for all GitHub-related tasks.›Requires the GitHub CLI (`gh`) authenticated in your project — it's how the command reads the issue.
How to add it
Copy the command file below.
Save it as .claude/commands/<name>.md in your project (create the folder if it doesn't exist).
Adjust anything project-specific (see the note below, if there is one).
Run the command in Claude Code by typing its name, e.g. it will appear in your / menu.
The linked repo is the source of truth — if the author updates it, the repo link stays current.