Fix issue
Skill viknesh20-20/claude-code-tool-kit/.claude/skills/fix-issue
Production-ready Claude Code configuration. 12 original agents, 200+ slash-command skills, 45+ MCP servers, 14 plugins, design + 3D + WebGPU + GSAP + RAG tooling. One-command Node.js installer for premium websites, SaaS apps, AI agents. Free, MIT, stack-agnostic.
npx -y skills add viknesh20-20/claude-code-tool-kit --skill fix-issueAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
2.0 KB, as published. Nobody here has run it
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
- Read the issue title, description, labels, and comments
- Identify: Is this a bug fix, feature request, or enhancement?
- Determine acceptance criteria — what does "done" look like?
- Note any linked issues, PRs, or referenced files
Step 2: Find Relevant Code
- Search the codebase for files/functions mentioned in the issue
- Trace the code path related to the reported behavior
- If it's a bug: try to reproduce the conditions mentally by reading the code
- 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
- Make the smallest change that addresses the issue
- Follow existing code patterns and conventions
- Add or update tests to cover the fix
- Ensure no regressions in adjacent functionality
Step 5: Verify
- Run existing tests for the affected area
- Run the new tests
- Review your own diff:
git diff - Check for unintended changes
Step 6: Commit and PR
- Stage changes:
git add <files> - Commit with reference:
git commit -m "fix: <description> (#<issue-number>)" - Push:
git push -u origin <branch> - 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