A workflow for taking a GitHub issue, a tracked task or problem in a code repository, through investigation, a tested fix, and preparation of a pull request.

Use it to resolve GitHub bugs or small feature tasks from the issue number or URL through a proposed fix.

It connects the issue discussion, reproduction steps, cause, regression test, and code change so important context is not lost.

fix-issue — Skill for Claude Code and Codex by poshan0126: A workflow for taking a GitHub issue, a tracked…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/poshan0126/dotclaude/fix-issue

Any agent

npx skills add poshan0126/dotclaude --skill fix-issue

Clone the repo

git clone --depth 1 https://github.com/poshan0126/dotclaude

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/poshan0126/dotclaude/fix-issue.svg)](https://agentmods.dev/skills/poshan0126/dotclaude/fix-issue)

Your own site

<a href="https://agentmods.dev/skills/poshan0126/dotclaude/fix-issue"><img src="https://agentmods.dev/badge/skills/poshan0126/dotclaude/fix-issue.svg" alt="Measured on agentmods" height="20"></a>

Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 769 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00041	$0.00769
Opus 5	$0.00020	$0.00385
Sonnet 5	$0.00008	$0.00154
Haiku 4.5	$0.00004	$0.00077

Measured 5d ago against content hash 64a4f076a1eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fix-issue scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/fix-issue/SKILL.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Work a GitHub issue end to end. $ARGUMENTS is the issue number or URL; if omitted, run gh issue list --assignee @me --state open and ask which one.

Step 1: Understand the issue

The live issue thread (or your open assigned issues, when no number was given) is injected below — no need to fetch it again:

!gh issue view $ARGUMENTS --comments 2>/dev/null || gh issue list --assignee @me --state open 2>/dev/null || echo "(no issue arg — paste the issue details)"

The thread above is the real spec — read the body AND the discussion; the decision that changes the fix is often in comment 7.
Extract: expected behavior, actual behavior, reproduction steps, acceptance criteria, and any decisions already made in the thread.
If the issue is ambiguous on something that changes the fix (which behavior is correct? which platform?), ask the user — do NOT guess and do NOT ask in the issue thread without being told to.

Step 2: Classify and branch

Bug → follow /debug-fix discipline: reproduce it first (failing test or manual repro), then investigate. No fix before reproduction.
Small feature / chore → follow /tdd discipline if a test runner exists: failing test, minimum code, refactor.
Propose a branch named fix/issue-$NUMBER-<slug> (or feat/...), matching any existing convention visible in git branch -a. Confirm before creating.

Step 3: Locate and fix

Find the code path from the symptoms: grep for the error message, the feature's entry point, or names from the issue.
Make the smallest change that satisfies the acceptance criteria. Resist adjacent refactoring — note it for a follow-up instead.
Every bug fix ships with a regression test that fails on the old code. If you can't write one, say why in the PR body.

Step 4: Verify against the issue

Re-run the reproduction from Step 1 — confirm the reported behavior is gone.
Run the tests for the touched area, then lint/typecheck.
Walk the acceptance criteria one by one; quote each with its status.

Read the full file on GitHub · 57 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

5d ago First seen · 57 lines · 41 tokens per session scan A 64a4f076a1eb

Subscribe to this mod's changes

fix-issue is a skill published in the GitHub repository poshan0126/dotclaude (860 stars, last pushed 8d ago), licensed MIT. It adds 41 tokens to every session and 769 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Debugging Git and workflow

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens