Skill

github-fix-issue

Fixes GitHub issues end-to-end with GitHub CLI: views issue, researches context, plans fix, creates branch, implements/tests changes, submits PR.

Git

Github

developer-tools

code-quality

npx claudepluginhub feiskyer/claude-code-settings --plugin claude-code-settings

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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.

SKILL.md

Similar Skills

github-issue-workflow

244

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.

4 files9 tools

developer-kit

team-collaboration-issue

682

Resolves GitHub issues through triage, root cause analysis, TDD, branch management, testing, and CI/CD-compliant pull requests. Ideal for team workflows on bugs and features.

1 file

rmyndharis-antigravity-skills

team-collaboration-issue

37.1k

Resolves GitHub issues via triage, root cause analysis, TDD implementation, branch management, testing, and CI/CD-compliant pull requests. Takes issue ID/URL.

1 file

antigravity-awesome-skills

Stats

Stars1496

Forks218

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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

# 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