Diagnose
Use when the user reports misbehaving software to investigate — a bug, crash, wrong output, flaky behavior, or '為什麼壞掉/不會動/查一下' — and the root cause is not yet established. Enforces building a red-capable reproduction command BEFORE any hypothesis is allowed, then 3-5 ranked falsifiable hypotheses before testing any single one. NOT for conceptual questions, code reading requests, or feature work. When a failing command already exists, Step 1 is pre-satisfied — still apply, jumping straight to the hypothesis discipline.
Install
npx skills add KerberosClaw/kc_ai_skills --skill diagnosegit clone --depth 1 https://github.com/KerberosClaw/kc_ai_skills.git /tmp/kc_ai_skills
mkdir -p ~/.claude/skills
cp -r /tmp/kc_ai_skills/diagnose ~/.claude/skills/diagnosePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# diagnose — 先架測謊機,再准審問 You are a disciplined debugger. 你最大的敵人不是 bug,是**自己的過早結論**:讀兩眼 code 就宣稱「找到原因了」,修下去症狀還在、信用先沒了。本 skill 的核心只有一件事——**Step 1 的 feedback loop 才是全部,其餘都是機械動作**。 ## Step 0: 適用判定 | 情境 | 套不套 | |---|---| | 行為異常(錯輸出 / crash / 時好時壞 / 效能劣化)且原因未明 | ✅ 套 | | 已有一條會 fail 的指令(失敗測試 / 可重現的 curl) | ✅ 套,既有指令當**候選 loop**——過一遍 Step 1 五條判準(常已滿足)再進 Step 3,必要時回 Step 2 最小化 | | 純概念問題、讀 code 導覽、新功能需求 | ❌ 不套 | | 原因已確立、只是要修 | ❌ 不套,直接修 | ## Step 1: 建 red-capable feedback loop(本 skill 的全部) **CRITICAL — 停止句:這條指令存在之前,禁止讀 code 建理論、禁止提任何 root cause。** 發現自己在沒有重現指令的狀態下開始「應該是因為…」——停,回來先建 loop。 ### 完成判準(五條全過才算有 loop) - [ ] 一條**實際跑過至少一次**的指令(把指令和輸出貼出來,不是「應該可以這樣測」) - [ ] **Red-capable**:它斷言的是 user 講的那個症狀(錯值、crash、缺資料),**不是「沒噴錯」** - [ ] 確定性:重跑結果一致(非決定性 bug → 目標改成**拉高重現率**——50% 可以 debug、1% 不行) - [ ] 秒級完成(分鐘級的 loop 會讓你懶得跑、開始用猜的) - [ ] 可無人執行(不需要 user 幫忙點畫面) ### Loop 手法選擇 | 情境 | 手法 | |---|---| | 有測試框架 | 寫一個 failing test | | HTTP 服務 | curl + 斷言輸出(grep / jq) | | CLI / script | 固定 fixture 輸入重跑 | | 只在特定資料上壞 | 把那筆資料抽成最小 fixture | | 版本回歸 | `git bisect` + 上面任一手法當判準 | | 效能問題 | **不用 log**,先量基準數字,再二分定位 | | 真的建不出來 | 最後手段:明講建不出、列出試過什麼、向 user 要環境 / log dump / 錄影——**不准在沒有 loop 的情況下開始猜** | ## Step 2: 最小化重現 逐項砍(環境變數、輸入欄位、config、資料量),**每砍一項重跑 loop**,直到剩下的每一項都缺它不可(砍掉任何一項就重現不了)。最小化省下的時間會在 Step 4 十倍還你。 ## Step 3: 假說——先列 3 到 5 個,再測第一個 **MANDATORY**: 測任何假說之前,先產出一張排序過的假說清單,每條附**可否證預測**: ``` H1(最可能):<假說>。若為真:跑 <X> 會看到 <Y>。 H2:... H3:... ``` - 排好的清單**先給 user 過目再開測**——user 常有能瞬間重排順序的領域知識。
Details
- Skill name
diagnose- Repository
- KerberosClaw/kc_ai_skills
- Path
diagnose/SKILL.md- License
- MIT
- Repo updated
- 14 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Diagnose skill do?
Use when the user reports misbehaving software to investigate — a bug, crash, wrong output, flaky behavior, or '為什麼壞掉/不會動/查一下' — and the root cause is not yet established. Enforces building a red-capable reproduction command BEFORE any hypothesis is allowed, then 3-5 ranked falsifiable hypotheses before testing any single one. NOT for conceptual questions, code reading requests, or feature work. When a failing command already exists, Step 1 is pre-satisfied — still apply, jumping straight to the hypothesis discipline.
How do I install the Diagnose skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add KerberosClaw/kc_ai_skills --skill diagnose. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Diagnose popular?
It lives in KerberosClaw/kc_ai_skills, which has 80 GitHub stars and 13 forks, and is included in 1 curated skill list.
Related skills
Adr
80KerberosClaw/kc_ai_skills
Use when a durable technical decision was just made in conversation and should be recorded, or when user asks to write/record an ADR (開 ADR / 記個決策 / 這要不要 ADR). Runs a three-gate check FIRST and actively talks the user out of writing one when the decision doesn't qualify — then writes a lightweight (title + 1-3 sentences) ADR following the repo's own ADR conventions if any exist. Repo conventions always override this skill's defaults. NOT for requirement specs (spec / prd-create) or rewriting historical decisions; preserve their text, allow evidence-backed current-state notes, and record change
Align
80KerberosClaw/kc_ai_skills
Reconcile existing repository documentation with the current implementation, especially after verified hotfixes or after QA in an unattended task. A manual run first asks whether to align only the docs a specific change touched (trigger scope) or rescan the whole repo; unattended runs use the scope the dispatch states and default to the whole repo. Follow cross-repo references for evidence; edit only documentation in the authorized repo, annotating conflicting historical records. Not for fixing code, deploying, inventing requirements, or building a new documentation suite.
Character Lora
80KerberosClaw/kc_ai_skills
Use when the user wants to build a consistent-identity LoRA for an original character — defining the character, generating a face/body-consistent multi-angle dataset (via the gpt-image-gen skill for codex image generation), captioning it, doing base-specific homework, training on a chosen base (Pony / Z-Image / others) on a local GPU, and producing a usable LoRA. This skill ORCHESTRATES the end-to-end pipeline and gates every expensive/irreversible step; it delegates actual image generation to gpt-image-gen and never improvises training settings from memory.
Documenting Python Libraries
115wdm0006/python-skills
Creates comprehensive Python library documentation including Google-style docstrings, Sphinx setup, API references, tutorials, and ReadTheDocs configuration. Use when writing docstrings, setting up Sphinx documentation, or creating user guides for Python libraries.
Designing Python Apis
115wdm0006/python-skills
Designs intuitive Python library APIs following principles of simplicity, consistency, and discoverability. Handles public re-exports, API evolution, deprecation, breaking changes, and error handling. Use when designing or reviewing a library API, exposing a symbol from a package __init__, or managing API versioning and deprecations.
Grill
80KerberosClaw/kc_ai_skills
Use when the user says 先討論 / wants to align on a fuzzy idea before building, or before any non-trivial implementation whose requirements are still ambiguous — interviews the user until shared understanding is confirmed, one question at a time, each with a suggested answer; facts answerable from the filesystem/code are looked up, never asked. Optionally maintains the repo's CONTEXT.md glossary when vocabulary settles during discussion. Also invoked by other skills (spec / prd-create) as their interviewing discipline. NOT for already-frozen specs (just implement) or for debugging (use diagnose).
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.