fix-issue
/fix-issue
Fetches a GitHub issue by number, analyzes the requirements, finds the relevant code, implements a fix, and optionally creates a PR. Use when working through your issue backlog.
- Author
- viknesh20-20 ↗
- Repository
- claude-code-tool-kit ↗
- Licence
- MIT
- Last repository change
- 02.05.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 02.05.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Fetches a GitHub issue by number, analyzes the requirements, finds the relevant code, implements a fix, and optionally creates a PR. Use when working through your issue backlog.
Arguments
/fix-issue [issue number]
Original author description
Fetches a GitHub issue by number, analyzes the requirements, finds the relevant code, implements a fix, and optionally creates a PR. Use when working through your issue backlog.
How it works
- Fetch Issue Details
- Workflow
- Rules
SKILL.md preview
--- name: fix-issue description: "Fetches a GitHub issue by number, analyzes the requirements, finds the relevant code, implements a fix, and optionally creates a PR. Use when working through your issue backlog." argument-hint: "[issue number]" allowed-tools: Read, Grep, Glob, Bash, Edit, Write --- # Fix GitHub Issue ## Fetch Issue Details !`gh issue view $1 2>/dev/null || echo "Usage: /fix-issue <issue-number> — requires gh CLI authenticated"` --- ## Workflow ### Step 1: Understand the Issue 1. Read the issue title, description, labels, and comments 2. Identify: Is this a **bug fix**, **feature request**, or **enhancement**? 3. Determine acceptance criteria — what does "done" look like? 4. Note any linked issues, PRs, or referenced files ### Step 2: Find Relevant Code 1. Search the codebase for files/functions mentioned in the issue 2. Trace the code path related to the reported behavior 3. If it's a bug: try to reproduce the conditions mentally by reading the code 4. Identify the minimal set of files that need to change ### Step 3: Create a Branch ``` git checkout -b fix/issue-<number>-<short-description> ``` ### Step 4: Implement the Fix 1. Make the smallest change that addresses the issue 2. Follow existing code patterns and conventions 3. Add or update tests to cover the fix 4. Ensure no regressions in adjacent functionality ### Step 5: Verify 1. Run existing tests for the affected area 2. Run the new tests 3. Review your own diff: `git diff` 4. Check for unintended changes ### Step 6: Commit and PR 1. Stage changes: `git add <files>` 2. Commit with reference: `git commit -m "fix: <description> (#<issue-number>)"` 3. Push: `git push -u origin <branch>` 4. Create PR: `gh pr create --title "Fix #<number>: <title>" --body "Closes #<number>"` --- ## Rules - Always reference the issue number in commits and PR - Don't scope-creep — fix only what the issue describes - If the issue is unclear, list your assumptions before implementing - If the fix requires architectural changes, flag it and discuss before proceeding
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · viknesh20-20/claude-code-tool-kit | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| pytorch/pytorch | 100 | BSD-3-Clause |
| leancodepl/patrol | 100 | Apache-2.0 |
| nvidia/nemo | 100 | Apache-2.0 |
| boogy/iam-policy-validator | 100 | MIT |
| umep-dev/suews | 100 | MPL-2.0 |
| mysticaltech/terraform-hcloud-kube-hetzner | 100 | MIT |
| stxrmik/antigravity-plus | 90 | MIT |
Database snapshot: 13.11.2026 · package version 05278fda1baa (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 88fix-github-issue
Fix a GitHub issue by number. Use when asked to fix GitHub issues. - 100fix-github-issue
Use when you have a GitHub Issue number or link and want it resolved end-to-end — reads the issue, locates the bug, applies a fix, writes tests, and opens a PR from the terminal. - 100agnostic-ai-gh-issue
Take one GitHub issue from branch to merged PR with TDD. Use when asked to work, fix, or implement an issue by number. - 100solve-issue
Solve a GitHub issue end-to-end and open a pull request. Use when the user wants to fix or resolve a specific GitHub issue (often by number or URL), or says "solve issue #123", "fix this issue", or "implement and PR this issue". - 100create-issue
This skill should be used when the user asks to "create an issue", "create a GitHub issue", "open an issue", "write up an issue", "file an issue", or after a design has been verified and needs to be captured as a trackable GitHub issue for implementation. Also handles updating… - 100github-issue-autofix
Implement a GitHub Issue fix on a branch and open a PR (Fixes #N). Use in conversation when the user gives an Issue number or URL and asks to implement or fix it. Also the L2 loop entry skill after autofix label, repository_dispatch, or workflow_dispatch. Interactive default is…