Diagnose Root
SkillDev toolsLets your agent diagnose stubborn bugs with a structured four-phase root cause investigation.
Available today. Use it from your connected AI after setup.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the Diagnose Root skill
About this skill
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.
What this skill tells your AI
The instructions your AI receives, as published by danielvm-git/bigpowers in skills/diagnose-root/SKILL.md and read by ahel’s review.
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 ]
Signals
- GitHub stars
- 248
- Forks
- 19
- Last commit
- Sep 2026
Advanced
- Item type
- skill
- Key
diagnose-root- Source
- github.com/danielvm-git/bigpowers