Fix Issue
Take a GitHub issue and actually resolve it end to end — read the issue, reproduce it, fix it in an isolated branch with a test, verify, and open a PR that closes the issue. The counterpart to /idea (which files issues): /idea captures, /fix-issue clears. Works off `gh` in whatever repo you're in. Triggers on `/fix-issue <number|url>`, "fix issue #N", "resolve this github issue", "pick up and fix issue N".
Install
npx skills add iamneilroberts/claude-skills --skill fix-issuegit clone --depth 1 https://github.com/iamneilroberts/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/fix-issue ~/.claude/skills/fix-issuePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# /fix-issue — resolve a GitHub issue, branch → fix → PR Turns a filed issue into a merge-ready change: understand, reproduce, fix with a test, verify, and open a PR that closes the issue. Never pushes or opens a PR without showing the diff first. ## Steps 1. **Load the issue.** Resolve the arg to an issue number (bare number or full URL). Read it and its discussion: ```bash gh issue view <n> --comments ``` Extract the actual problem, repro steps, acceptance criteria, and linked PRs/commits. If the issue is vague or already closed, say so and ask before proceeding — don't guess at scope. 2. **Confirm scope (one beat).** State in one or two lines what you're changing and what "done" means for this issue. If the issue is really several changes, do the smallest coherent one and note the rest. Don't expand scope beyond what the issue asks. 3. **Isolate the work.** Create a dedicated branch/worktree so this doesn't collide with other work. Prefer the `branch` skill if it's installed (`/branch fix-<n>-<slug>`); otherwise `git worktree add`, or at minimum `git checkout -b fix-<n>-<slug>`. Check `git status` first — never start on top of another session's uncommitted WIP. 4. **Reproduce before fixing** (for a bug). Write a failing test that captures the issue, or otherwise demonstrate the broken behavior concretely — a fix with no reproduction is a guess.
Details
- Skill name
fix-issue- Repository
- iamneilroberts/claude-skills
- Path
skills/fix-issue/SKILL.md- Repo updated
- 21 August 2026
FAQ
What does the Fix Issue skill do?
Take a GitHub issue and actually resolve it end to end — read the issue, reproduce it, fix it in an isolated branch with a test, verify, and open a PR that closes the issue. The counterpart to /idea (which files issues): /idea captures, /fix-issue clears. Works off `gh` in whatever repo you're in. Triggers on `/fix-issue <number|url>`, "fix issue #N", "resolve this github issue", "pick up and fix issue N".
How do I install the Fix Issue skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add iamneilroberts/claude-skills --skill fix-issue. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Fix Issue popular?
It lives in iamneilroberts/claude-skills, which has 37 GitHub stars and 7 forks.
Related skills
Brag
37iamneilroberts/claude-skills
Memorialize something you just built by generating a self-contained "showcase" page for it — a persuasive, good-looking deep dive: what it is, why it's impressive, how it works — with a screenshot if one can be found or captured, and links to related showcase pages. This is the sales/hype-leaning counterpart to /write-post (which drafts a neutral, no-BS technical post); reach for /brag when you want it to sell. Fast by design, like /idea: ask only what's needed, build the page, don't turn it into a project. Triggers on `/brag <subject>`, "brag about this", "make a showcase page for X", "write
Branch
37iamneilroberts/claude-skills
Create an isolated git worktree for a task and log it to a shared work journal, so multiple Claude Code sessions run in parallel without racing on HEAD, uncommitted edits, or the index. Subcommands: `list`, `done <slug>`, `update` (heartbeat), `coord <message>` / `coord clear <slug>` (cross-session constraints). Triggers on `/branch`, "start in a worktree", "isolate this work", "parallel session", "heartbeat the journal".
Claude Code Best Practices
37iamneilroberts/claude-skills
Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.
Github Review
37iamneilroberts/claude-skills
Review a GitHub pull request — the PR-review behavior that used to live in the built-in `/review`, split out now that `/review` is the review orchestrator. Fetches the PR with `gh`, reviews the diff at an evidence-graded bar (only a fully-traced finding is blocking), and optionally posts inline PR comments. For your uncommitted working diff use `/review` instead; this command is specifically for a PR. Triggers on `/github-review`, `/github-review <pr>`, "review this pull request", "review PR #N".
Curate
37iamneilroberts/claude-skills
Verify a session's or handoff's factual claims against ground truth before trusting them. Dispatches the read-only `curator` subagent to check claims against git, files, and read-only environment checks, plus the repo's invariants doc if any, and returns a confabulation report for human spot-check. Use at pass boundaries — resuming from a handoff, before a deploy, or whenever a prior session's summary looks suspiciously clean. Triggers on `/curate`, "curate this", "verify these claims", "check the handoff for confabulation", "is this actually done".
Idea
37iamneilroberts/claude-skills
Capture a fix / feature / research idea fast and turn it into a tracked GitHub Issue plus a lightweight planning doc, so nothing gets lost and it shows up next time you list your issues. Runs a short confirm-or-edit interview (infers title/slug/type from your one-liner, you accept or correct), writes docs/ideas/<date>-<slug>.md, files a labelled GitHub Issue via gh, and backlinks the issue URL into the doc. Triggers on `/idea <one-liner>`, `/idea`, "capture this idea", "file an idea", "log a thing to fix/build/research", "remember to look into X".
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.