fix-bug

A five-step workflow for diagnosing and fixing a newly discovered software bug. It traces the symptom through the data flow, checks the wider impact, proposes a fix, and verifies the result.

In plain words
What is it for?
Use it for errors, broken behavior, or features that cannot be used, especially when you need reproduction steps, root-cause analysis, a repair plan, and validation.
Why use it?
It prevents changing only the file where an error appears without understanding the underlying cause or other affected code. After two unsuccessful fixes, it switches to a more thorough stuck-bug process.

Command

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 commands/xcodethink/open-claude-code-skills/fix-bug
Clone the repo
git clone --depth 1 https://github.com/xcodethink/open-claude-code-skills
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 296 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.

ModelPer sessionOnce invoked
Fable 5 $0.00026 $0.00296
Opus 5 $0.00013 $0.00148
Sonnet 5 $0.00005 $0.00059
Haiku 4.5 $0.00003 $0.00030

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

Security

Grade A, and why

fix-bug 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 2d 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.

commands/fix-bug.md · 27 lines

What it actually says

fix-bug — 修 bug 标准 5 步流程

用户输入 /fix-bug $ARGUMENTS 触发 标准 5 步分析(适合首次发现的 bug)。

立刻读取并完整加载: ~/.claude/prompts/lib/02-诊断/标准修bug.md

按其"行为契约"段严格执行:

  1. 完整读症状(自己复现)
  2. 追数据流到源头
  3. grep 全局影响面
  4. 输出完整诊断(症状/复现/根因/影响范围/修复方案/验证方式)→ 等用户 yes
  5. 一次性修复 + 自验证

修了 2 次还没解决 → 切到 /stuck-bug 模板(强制重启)。

参数 $ARGUMENTS 含修饰符 → 叠加对应文件。

核心契约:禁止见症状就动手,禁止穷举试方案,禁止只改报错那一个文件。

参数: $ARGUMENTS

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. 2d ago First seen · 27 lines · 0 tokens per session scan A f89a44a6e659

Subscribe to this mod's changes

fix-bug is a command published in the GitHub repository xcodethink/open-claude-code-skills (2 stars, last pushed 27d ago), licensed MIT. It adds 26 tokens to every session and 296 once invoked, about $0.0001 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-31.