Diagnose Root

Diagnose Root is a Quality skill for Claude Code, published by danielvm-git in bigpowers.

173 stars14 forkson danielvm-git/bigpowersAdded 2026/09/07+8% in starsRepository updated 2026/09/06

ai-agentsautomationbmadclaude-codeclean-codecursor-rulesdevopsdocumentation-as-codegemini-cliproductivitysoftware-engineeringsolo-developerspec-driven-developmenttdd

Install in seconds

Install Diagnose Root

Copy Diagnose Root into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/danielvm-git/bigpowers/tree/main/skills/diagnose-root ~/.claude/skills/diagnose-root

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/danielvm-git/bigpowers.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/diagnose-root/SKILL.md in danielvm-git/bigpowers
Installs to: ~/.claude/skills/diagnose-root
Collection: One of 23 skills cataloged from this repository
Category: Quality — 1817 skills

What Diagnose Root does

Diagnose Root runs a four-phase root cause analysis for confirmed bugs: reproduce, isolate, hypothesize, and verify. Use it when the cause is unclear and you need evidence before proposing a fix.

Diagnose Root is cataloged under Quality on DirSkills. Diagnose Root comes from a repository tagged ai-agents, automation, bmad, claude-code and clean-code.

Documentation

README

Excerpt

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.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Diagnose Root

What else does danielvm-git publish alongside Diagnose Root?
Diagnose Root is one of 23 skills that DirSkills catalogs from danielvm-git/bigpowers, the repository it ships in. Its siblings there include Align Grid, Assess Impact and Audit Code. Each one is a separate skill with its own page in this directory, installs the same way Diagnose Root does, and is maintained by danielvm-git in that same repository. The rest of the collection is listed on the danielvm-git/bigpowers page.
How does Diagnose Root compare to other Quality skills?
Diagnose Root ranks #1730 by stars among the 1817 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Diagnose Root against them. Open each page to compare what they document and how they install.