From Claude Code Settings
Fix GitHub issues end-to-end — analysis, branch creation, implementation, testing, and PR submission.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-code-settings:github-fix-issueThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A structured workflow for analyzing, fixing, and submitting a PR for a GitHub issue. This skill uses the GitHub CLI (`gh`) for all GitHub interactions.
A structured workflow for analyzing, fixing, and submitting a PR for a GitHub issue. This skill uses the GitHub CLI (gh) for all GitHub interactions.
gh issue view <number> to get full issue details (title, body, labels, comments)Before jumping into code, gather context — understanding what's been tried or discussed prevents duplicate work and surfaces useful patterns:
gh pr list --search "<keywords>"Think through how to break the issue into small, manageable tasks. Document your plan in a scratchpad file:
fix/issue-123-description)Thorough testing prevents the fix from introducing new problems:
gh pr create# View issue details
gh issue view 123
# Create a branch
git checkout -b fix/issue-123-description
# Open a PR that closes the issue
gh pr create --title "Fix: description" --body "Fixes #123"
# Request review
gh pr edit 456 --add-reviewer username
npx claudepluginhub skarlso/claude-code-settings2plugins reuse this skill
First indexed Jul 13, 2026
Fix GitHub issues end-to-end — analysis, branch creation, implementation, testing, and PR submission.
Resolves GitHub issues via 8-phase workflow: fetch details, analyze requirements, implement solutions, verify correctness, code review, commit changes, create PRs. Activates on resolve, implement, fix requests or issue references.
Resolves GitHub issues via systematic triage, root cause analysis, test-driven development, and PR management. Includes playbook references for detailed patterns.