Github Fix Issue

Name: Github Fix Issue
Author: feiskyer

feiskyer/claude-code-settings

142 installs
1.6k repo stars
Updated July 27, 2026
feiskyer/claude-code-settings

Turn a GitHub issue into a fix: read reproduction steps, edit the repo, run checks, and open a linked pull request with minimal manual handoff from the issue tracker.

About

Orchestrates end-to-end GitHub issue resolution: ingest issue title and body, infer or reproduce the bug, modify the codebase, run relevant checks, and open a pull request that references the original issue. Built for Claude Code agents maintaining product or open-source repos with consistent fix workflows.

Issue context parsing and reproduction
Branch creation from tracker metadata
Targeted code patch generation
Test and lint awareness before PR
Auto-linked PR referencing the issue

Github Fix Issue by the numbers

142 all-time installs (skills.sh)
Ranked #191 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
Data as of Aug 5, 2026 (Skillselion catalog sync)

npx skills add https://github.com/feiskyer/claude-code-settings --skill github-fix-issue

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/feiskyer/claude-code-settings/github-fix-issue.svg)](https://skillselion.com/skills/feiskyer/claude-code-settings/github-fix-issue)

Installs	142
repo stars	★ 1.6k
Last updated	July 27, 2026
Repository	feiskyer/claude-code-settings ↗

What it does

Turn a GitHub issue into a fix: read reproduction steps, edit the repo, run checks, and open a linked pull request with minimal manual handoff from the issue tracker.

Files

SKILL.mdMarkdownGitHub ↗

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