A structured process helps you turn a GitHub issue into a working pull request. This skill guides you through eight clear phases from reading the issue to submitting your code. It keeps your work safe by treating issue text as untrusted content.
You start by fetching the issue details and then analyzing the requirements with the user. After getting confirmation, you implement the solution, verify correctness, and review the code. Finally you commit changes and create a pull request.
This workflow is designed for developers who want a repeatable way to resolve GitHub issues. It uses the GitHub CLI and includes security gates to prevent accidental execution of harmful instructions from issue bodies. Every step is clearly defined so you can focus on writing good code.
Global
mkdir -p ~/.claude/skills/github-issue-workflowProject
mkdir -p .claude/skills/github-issue-workflowSource Repository
Caveman Commitjuliusbrussee/caveman
Generate ultra-compressed commit messages with Conventional Commits format
Verification Before Completionobra/superpowers
Always run fresh verification before claiming work is complete or passing
Using Git Worktreesobra/superpowers
Isolate your feature work with git worktrees and keep your main branch safe
Finishing A Development Branchobra/superpowers
Finish your development branch with merge, pull request, or cleanup options
Git Guardrails Claude Codemattpocock/skills
Stop dangerous git commands from running automatically with safety hooks
Setup Pre Commitmattpocock/skills
Automate code formatting type checking and tests before every commit
Git Commitgithub/awesome-copilot
Automatically write standardized git commits by analyzing your code changes
Git Advanced Workflowswshobson/agents
Master advanced Git workflows for clean history and confident recovery