root-cause-analysis · markpitt — Claude Code skill: analysis and install
The root-cause-analysis skill guides investigations with 5 Whys, Ishikawa diagrams, Pareto analysis, and fault trees. Use it to trace a bug or failure beyond its visible symptoms.
no license 107 installs ★ 25 updated 2026-02-19
npx skills add markpitt/claude-skills --skill root-cause-analysis -a claude-codeWhat root-cause-analysis does
The skill starts by shaping a clear problem statement: what happened, where, when, and with what impact. It then matches the investigation to the situation. A straightforward failure chain can use 5 Whys; several plausible causes call for an Ishikawa diagram. Start with evidence.
Files under resources/ explain the methods, catalog common causes by domain, and provide worked cases. Advanced material covers fault trees and barrier analysis. During an investigation, the skill guides evidence gathering, records the reasoning, and checks conclusions with forward and backward tests. Without observations or evidence about the issue, the analysis has little concrete material to test.
What it helps with
- trace a software failure to its underlying cause
- investigate a chain of equipment failures
- sort possible causes of a process breakdown
- test an analysis against available evidence
Example prompts for the agent
- Investigate the failure after the latest deployment and help me trace its root cause.
- Use 5 Whys on this error, then check the conclusion against the logs.
- Build an Ishikawa diagram for the service failures that keep recurring.
How to install root-cause-analysis
1Skills CLI (Vercel)
npx skills add markpitt/claude-skills --skill root-cause-analysis -a claude-code2Manually: put the files in place
~/.claude/skills/root-cause-analysis/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/root-cause-analysis/
1Skills CLI (Vercel)
npx skills add markpitt/claude-skills --skill root-cause-analysis -a codex2Manually: put the files in place
.agents/skills/root-cause-analysis/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add markpitt/claude-skills --skill root-cause-analysis -a cursor2Manually: put the files in place
.cursor/skills/root-cause-analysis/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install markpitt/claude-skills skills/root-cause-analysis2Manually: put the files in place
.github/skills/root-cause-analysis/SKILL.md1Skills CLI (Vercel)
npx skills add markpitt/claude-skills --skill root-cause-analysis -a gemini-cli2Platform CLI
gemini skills install https://github.com/markpitt/claude-skills --path skills/root-cause-analysisManually: put the files in place
.devin/skills/root-cause-analysis/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add markpitt/claude-skills --skill root-cause-analysis -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about root-cause-analysis
How do I install root-cause-analysis in Claude Code?
Run npx skills add markpitt/claude-skills --skill root-cause-analysis -a claude-code. The skill file is at ~/.claude/skills/root-cause-analysis/SKILL.md.
What does root-cause-analysis do?
It helps investigate an issue, choose an analysis method, and test the conclusion against evidence. Its methods include 5 Whys, Ishikawa diagrams, Pareto analysis, and fault trees.
Which method should I use for a complex issue?
For a problem with several plausible causes, the skill recommends starting with an Ishikawa diagram and then using 5 Whys. Fault tree analysis is intended for critical or high-stakes cases.
Similar skills
All skills for Testing and QA →root-cause-analysis by other authors comes first.