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.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 289
- Forks
- 24
01 前言 Front Matter
- 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.
03 SKILL.md 正文
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 ]
04 同仓库更多 Skills
skill-verify-fail-open-fixture
Negative-path fixture for run-skill-verify.sh — must never PASS.
negative-path
暂无简介
write-document
Write, organize, and sync high-integrity technical documents using the BMAD methodology. Ensures every document is Bold, Minimal, Actionable, and Durable. Use when creating architectural docs, technical guides, or organizing the specs/ directory.
wire-observability
Add structured JSON logging, observability commands, and idempotent setup scripts to a project. Use when a project needs production-readiness instrumentation, when user wants structured logging, or as a production-readiness gate at any phase of development.
wire-ci
CI pipeline setup with bundled, forge-neutral templates and local validation. Detects the forge from the git remote, generates workflows for supported forges, and skips honestly for the rest. The CI equivalent of wire-observability.
visual-dashboard
Start a browser-based dashboard that visualizes architecture, implementation plans, and project status. Persists artifacts in .bigpowers/dashboard/. Reads specs/state.yaml, release-plan.yaml, epics, and planning-status via HTTP API or opencode panel.