dev: Command for Claude Code

.claude/commands/fix-issue.md

fix-issue is a command for Claude Code from squirrelsoft-dev/dev. It costs 10 tokens per session (198 once invoked), scanned A, original, MIT.

A workflow for taking a GitHub issue from its description to a tested fix and pull request. GitHub is a service for hosting code and tracking issues; a pull request is a proposed change for review.

In plain words
What is it for?
Use it to analyze an issue, identify the affected code, create a branch, implement the smallest fix, run tests, commit the change, and open a pull request.
Why use it?
It keeps investigation, implementation, testing, commits, and issue linking in one repeatable process. This reduces the chance of fixing the wrong problem or forgetting a regression test.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is squirrelsoft-dev/dev's own configuration. It tells Claude Code how to work on dev itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dev configures →

Reuse

Borrowing it

Nothing to install: this file belongs to squirrelsoft-dev/dev. 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/squirrelsoft-dev/dev/main/.claude/commands/fix-issue.md
Clone the repo
git clone --depth 1 https://github.com/squirrelsoft-dev/dev

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.

agentmods badge for fix-issue

README.md
[![agentmods](https://agentmods.dev/badge/commands/squirrelsoft-dev/dev/fix-issue/github.svg)](https://agentmods.dev/commands/squirrelsoft-dev/dev/fix-issue)
Your own site
<a href="https://agentmods.dev/commands/squirrelsoft-dev/dev/fix-issue"><img src="https://agentmods.dev/badge/commands/squirrelsoft-dev/dev/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.

agentmods 80×15 button for fix-issue

Your own site · 80×15
<a href="https://agentmods.dev/commands/squirrelsoft-dev/dev/fix-issue"><img src="https://agentmods.dev/badge/commands/squirrelsoft-dev/dev/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 198 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.00198
Opus 5.5 $0.00004 $0.00079
Sonnet 5.5 $0.00002 $0.00040
Haiku 4.5 $0.00001 $0.00020

Measured 1mo ago against content hash 10165f2f94da, 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 · 21 lines

What it actually says

Fix GitHub Issue

Resolve issue $ARGUMENTS from analysis through PR creation.

Steps

  1. Fetch — gh issue view $ARGUMENTS to get the full issue context.
  2. Analyze — Identify affected files, root cause, and reproduction steps.
  3. Branch — Create fix/issue-$ARGUMENTS from latest main.
  4. Implement — Make the minimal fix following existing code patterns.
  5. Test — Write a regression test that fails without the fix and passes with it.
  6. Verify — Run the full test suite. Ensure no regressions.
  7. Commit — Use conventional commit format referencing the issue.
  8. PR — Create a PR that auto-closes the issue with full context.

Keep the change minimal. Fix the bug, add the test, nothing else.

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.

  1. 1mo ago First seen · 21 lines · 10 tokens per session scan A 10165f2f94da

Subscribe to this mod's changes

fix-issue is a command published in the GitHub repository squirrelsoft-dev/dev (17 stars, last pushed 5d ago), licensed MIT. It adds 10 tokens to every session and 198 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-01.