Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add markpitt/claude-skills --skill root-cause-analysis -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/root-cause-analysis/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/root-cause-analysis/

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.

root-cause-analysis aj-geddes root-cause-analysis — a skill that walks an incident down to the cause you can actually fix, instead of patching the symptom again. CX Codex +1 940installs root-cause-analysis autohandai root-cause-analysis is a Claude Code skill that investigates outages, regressions, and recurring failures by tracing evidence to design flaws. It drafts postmortems with timelines and prevention tasks. CX Codex +1 ★ 219repo stars 022-root-cause-analysis Juan Antonio Breña Moral 022-root-cause-analysis — a skill for Claude Code, Codex, Cursor, GitHub Copilot, and Gemini CLI that runs structured root cause analysis using Five Whys, Fishbone (Ishikawa), and Current Reality Tree. CX Codex +1 144installs cause-and-effect NeoLabHQ cause-and-effect runs structured Ishikawa diagram investigations on development bottlenecks. Pinpoints root causes across technical and team factors. CX Codex +1 1,300installs root-cause-analyst SuperClaude-Org The root-cause-analyst subagent for Claude Code systematically investigates failures and complex errors by collecting evidence and testing hypotheses. It finds root causes rather than patching symptoms. CX Codex ★ 23,950repo stars diagnosing-root-causes b-mendoza The diagnosing-root-causes skill traces bugs, regressions, and CI/CD failures from supplied evidence, then produces a reviewed root-cause report. Use it when a problem report needs investigation rather than guesswork. CX Codex +1 122installs root-cause-analyzer alirezarezvani root-cause-analyzer — a subagent for methodical root cause analysis of bugs, performance issues, and production failures. Deploy when you need to understand why code breaks, not just patch the symptom. CX Codex ★ 788repo stars root-cause-tracing NeoLabHQ root-cause-tracing — a skill that walks the agent backward through the call stack until it finds the original trigger, then fixes there instead of at the crash site. CX Codex +1 1,400installs

From the same set10

The whole set →
avalonia Guides an agent through Avalonia work: MVVM, XAML, bindings, styling, controls, and platform-specific code for .NET applications. CX Codex +1 286installs microsoft-graph A hub for Microsoft Graph work: eight reference files, shared query parameters and permission rules. Useful when the agent is writing a Microsoft 365 integration. CX Codex +1 263installs kiss-principle The kiss-principle skill helps spot needless complexity in code and design, then plan simpler solutions without dropping required behavior. Use it during reviews, refactors, or feature planning. CX Codex +1 251installs markdown-formatter markdown-formatter rewrites the markup of a markdown file against one set of style rules, then checks the result with a bundled script and reports what changed. CX Codex +1 245installs azure-devops Guides an agent through Azure DevOps REST API work across Boards, Repos, Pipelines, Test Plans, and Artifacts. Useful for integrations and DevOps automation. CX Codex +1 191installs github-api github-api routes GitHub REST and GraphQL requests through dedicated reference guides. Helps build integrations, automate pull requests, and trigger Actions without leaking tokens. CX Codex +1 148installs gof-design-patterns gof-design-patterns finds the right Gang of Four pattern for the problem you describe and writes a working implementation in one of eight languages. CX Codex +1 145installs dotnet-aspire The dotnet-aspire skill helps add .NET Aspire to an existing .NET solution, including its orchestration and shared service setup. Use it when wiring a distributed app. CX Codex +1 104installs

Project sponsors

Companies that keep this analytics open