github-fix-issue
The github-fix-issue skill orchestrates a complete GitHub issue resolution workflow, executing steps from initial issue analysis through branch creation, implementation, testing, and pull request submission using GitHub CLI commands. Use this when addressing any GitHub issue, bug report, or numbered issue reference that requires code changes and a formal pull request.
git clone --depth 1 https://github.com/feiskyer/claude-code-settings /tmp/github-fix-issue && cp -r /tmp/github-fix-issue/skills/github-fix-issue ~/.claude/skills/github-fix-issueSKILL.md
# Fix GitHub Issue 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. ## Workflow ### 1. Understand the Issue - Run `gh issue view <number>` to get full issue details (title, body, labels, comments) - Read through the problem description carefully - If the issue is unclear or missing key details, ask the user clarifying questions before proceeding ### 2. Research Prior Art Before jumping into code, gather context — understanding what's been tried or discussed prevents duplicate work and surfaces useful patterns: - Search the codebase for files and functions related to the issue - Check if related PRs exist with `gh pr list --search "<keywords>"` - Look for scratchpads or notes from previous investigation - Read relevant source files to understand the current behavior ### 3. Plan the Fix Think through how to break the issue into small, manageable tasks. Document your plan in a scratchpad file: - Name the file descriptively (include the issue reference) - Include a link back to the issue - List the specific changes needed and their order - Note any risks or edge cases ### 4. Implement - Create a new branch for the issue (e.g., `fix/issue-123-description`) - Work through the plan in small steps - Commit after each meaningful change — small commits are easier to review and revert ### 5. Test Thorough testing prevents the fix from introducing new problems: - Write unit tests that describe the expected behavior - Run the full test suite to catch regressions - If UI changes were made and browser automation (e.g., Puppeteer MCP) is available, use it to verify visually - Fix any failing tests before moving on ### 6. Open Pull Request - Push the branch and open a PR with `gh pr create` - Reference the issue in the PR description (e.g., "Fixes #123") - Request a review ## gh Command Reference ```sh # 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 ```
Create Claude Code custom slash commands with proper structure, frontmatter, and best practices. Use this skill whenever the user wants to create a new command, add a slash command, build a custom command, or mentions "create-command", "new command", "add command", or "make a command" for Claude Code. Also trigger when the user wants to turn a workflow into a reusable command.
Comprehensive session analysis and learning capture specialist. Analyzes development sessions to extract patterns, preferences, and improvements for future interactions. Use after significant work sessions to capture learnings.
GitHub issue resolution specialist. Analyzes, plans, and implements fixes for GitHub issues with proper testing and PR creation. Use when fixing specific GitHub issues.
Technical breakthrough documentation specialist. Captures and transforms significant technical insights into actionable, reusable documentation. Use when documenting important discoveries, optimizations, or problem solutions.
Analyzes and improves Claude Code instructions in CLAUDE.md. Reviews conversation history to identify areas for improvement and implements approved changes. Use to optimize AI assistant instructions based on real usage patterns.
Expert code reviewer for GitHub pull requests. Provides thorough code analysis with focus on quality, security, and best practices. Use when reviewing PRs for code quality and potential issues.
Expert UI/frontend developer for creating, modifying, or reviewing frontend code, UI components, and user interfaces. Use when building React components, responsive designs, or any frontend development tasks. PROACTIVELY use for UI/UX implementation, component architecture, and frontend best practices.
>-