A guided command for investigating and fixing a GitHub issue, a tracked bug or task in a repository. It first reproduces the problem, traces its cause in the code, and applies a focused fix.

Use it when you have a GitHub issue number and want to reproduce the problem, find its root cause, make the smallest suitable change, and summarise the result.

It reduces guesswork and discourages unrelated code changes while fixing an issue. It also gives the change a defined check and formatting step before it is reported.

How ikhanux/ai-coding-blueprint configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to ikhanux/ai-coding-blueprint. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ikhanux/ai-coding-blueprint/main/.claude/commands/fix-issue.md

Clone the repo

git clone --depth 1 https://github.com/ikhanux/ai-coding-blueprint

Made for: Claude Code.

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/commands/ikhanux/ai-coding-blueprint/fix-issue/github.svg)](https://agentmods.dev/commands/ikhanux/ai-coding-blueprint/fix-issue)

Your own site

<a href="https://agentmods.dev/commands/ikhanux/ai-coding-blueprint/fix-issue"><img src="https://agentmods.dev/badge/commands/ikhanux/ai-coding-blueprint/fix-issue/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/ikhanux/ai-coding-blueprint/fix-issue"><img src="https://agentmods.dev/badge/commands/ikhanux/ai-coding-blueprint/fix-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00010	$0.00152
Opus 5.5	$0.00004	$0.00061
Sonnet 5.5	$0.00002	$0.00030
Haiku 4.5	$0.00001	$0.00015

Measured 1mo ago against content hash b0d65c3ccd44, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

.claude/commands/fix-issue.md · 17 lines

What it actually says

!gh issue view $ARGUMENTS

Investigate and fix the issue above.

Reproduce it first, using the Run / Check / Test commands from CLAUDE.md § Commands
Trace the bug to its root cause: read the actual code, don't guess (delegate to debugger if the cause isn't obvious)
Implement the minimal fix; no drive-by refactors
Run the Check command, then the Format command on touched files if one exists
Summarise what you changed and why, referencing the issue number

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.

1mo ago First seen · 17 lines · 10 tokens per session scan A b0d65c3ccd44

Subscribe to this mod's changes

fix-issue is a command published in the GitHub repository ikhanux/ai-coding-blueprint (2 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 152 once invoked, about $0.0000 per session on Opus 5.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-09-21.

Debugging Git and workflow

fix-issue next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
fix-issueikhanux/ai-coding-blueprint	Command	2	1mo ago	MIT	A	10	Claude Code
barista-fixfrappe/frappe-ui	Command	1.1k	2d ago	MIT	A	17	Claude Code
fix-issueyonatangross/orchestkit	Command	299	yesterday	MIT	A	45	Claude Code, Cursor
unbloatathola/claude-night-market	Command	348	yesterday	MIT	A	27	Claude Code
payload-revertopenshift-eng/ai-helpers	Command	122	yesterday	Apache-2.0	A	12	Claude Code
AGENTSmax-sixty/worktrunk	Command	12k	yesterday	none	A	0	Claude Code
fix-issuefltman/project-scaffolder	Command	88	9d ago	MIT	A	0	Claude Code

ai-coding-blueprint: Command for Claude Code