Borrowing it
Nothing to install: this file belongs to u9401066/rootcause-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/u9401066/rootcause-mcp/master/.claude/skills/bug-fix/SKILL.mdgit clone --depth 1 https://github.com/u9401066/rootcause-mcpWrote 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.
[](https://agentmods.dev/skills/u9401066/rootcause-mcp/bug-fix)<a href="https://agentmods.dev/skills/u9401066/rootcause-mcp/bug-fix"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/bug-fix/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.
<a href="https://agentmods.dev/skills/u9401066/rootcause-mcp/bug-fix"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/bug-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.01489 |
| Opus 5.5 | $0.00000 | $0.00596 |
| Sonnet 5.5 | $0.00000 | $0.00298 |
| Haiku 4.5 | $0.00000 | $0.00149 |
Grade A, and why
bug-fix 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.
This is a copy
100% identical to bug-fix — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug 修復工作流
描述
結構化的 Bug 修復流程，包含根因分析和回歸測試。
觸發條件
- 「修 bug」「fix bug」「除錯」
- 「BF: [問題描述]」
🐛 Bug 修復流程
┌─────────────────────────────────────────────────────────────┐
│ Bug Fix Workflow │
├─────────────────────────────────────────────────────────────┤
│ Step 1: 🔍 重現 (Reproduce) │
│ ├─ 確認重現步驟 │
│ ├─ 收集錯誤訊息/日誌 │
│ └─ 建立最小重現案例 │
├─────────────────────────────────────────────────────────────┤
│ Step 2: 🎯 定位 (Locate) │
│ ├─ 分析錯誤堆疊 │
│ ├─ 追蹤程式碼路徑 │
│ └─ 識別問題根因 │
├─────────────────────────────────────────────────────────────┤
│ Step 3: 🧪 測試先行 (Test First) │
│ ├─ 撰寫失敗的測試案例 │
│ ├─ 確認測試能重現問題 │
│ └─ 這將成為回歸測試 │
├─────────────────────────────────────────────────────────────┤
│ Step 4: 🔧 修復 (Fix) │
│ ├─ 實施修復 │
│ ├─ 最小化變更範圍 │
│ └─ 確認測試通過 │
├─────────────────────────────────────────────────────────────┤
│ Step 5: ✅ 驗證 (Verify) │
│ ├─ 執行完整測試套件 │
│ ├─ 檢查是否引入新問題 │
│ └─ [code-reviewer] 審查修復 │
├─────────────────────────────────────────────────────────────┤
│ Step 6: 📝 記錄 (Document) │
│ ├─ 更新 Memory Bank │
│ ├─ 記錄根因分析 │
│ └─ 更新相關文檔 │
└─────────────────────────────────────────────────────────────┘
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 · 171 lines · 0 tokens per session scan A fa0c0d0b3d5c
bug-fix is a skill published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,489 tokens. A static security scan graded it A with 0 findings. It is 100% identical to bug-fix, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
bug-fix
A structured process for fixing software bugs, including reproducing the problem, finding its root cause, and writing a test that prevents it from returning. A regression test is an automated check that catches a previously fixed problem.
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error. Also load when a live run you started for the user fails with an error from…
n8n-docs-assistant
Answers n8n product, setup, credential, node, hosting, API, and usage questions from current n8n docs. Use when the user asks how to configure, set up, troubleshoot, or understand n8n behavior, especially credential setup questions — including which OAuth scopes or permissions a provider app needs.
sentry-sdk-upgrade
Upgrade the Sentry JavaScript SDK across major versions. Use when asked to upgrade Sentry, migrate to a newer version, fix deprecated Sentry APIs, or resolve breaking changes after a Sentry version bump.
dorodango
Polishes working code through successive quality passes in fresh subagents. Use after tests pass when code needs multi-dimension refinement before release.
extracting-code-structure
Use when listing all methods, functions, or classes in a file, exploring unfamiliar code, getting API overviews, or deciding what to read selectively without loading entire files.