浏览器与自动化
diagnose-root
Run 4-phase root cause analysis — reproduce, isolate, hypothesize, verify. Use when a bug is confirmed but root cause is unclear, after investigate-bug, or when user mentions root cause analysis.
danielvm-git · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add danielvm-git/bigpowers --skill diagnose-root技能说明
name: diagnose-root model: sonnet description: "Run 4-phase root cause analysis — reproduce, isolate, hypothesize, verify. Use when a bug is confirmed but root cause is unclear, after investigate-bug, or when user mentions root cause analysis."
Diagnose Root
Boundary: Canonical, reusable 4-phase RCA engine. Invoked by investigate-bug (as step 2 of the end-to-end flow) and by fix-bug (when no bug file exists). Does not write the bug file — that is investigate-bug's responsibility.
Four phases — do not skip. Update the active specs/bugs/BUG-*.md file at each phase.
Phases
- Reproduce — minimal steps; record environment; capture logs.
- Isolate — narrow to module/function; binary-search commits or config.
- Hypothesize — list ranked hypotheses with falsification test each.
- Verify — run falsification; confirm single root cause; link to fix plan.
HARD GATE — Do not propose a fix until phase 4 confirms one root cause with evidence.
Verify
→ verify: [ "$(grep -lE 'Reproduce' specs/bugs/BUG-*.md 2>/dev/null | grep -cv "\.okf\.md$")" -ge 1 ]