Skip to main content

/

/

Stats

Actions

Tags

Stats

Actions

Tags

ClaudePluginHub

Community directory for discovering and installing Claude Code plugins.

Find plugins for your project

AI-powered recommendations based on your stack.

Product

Browse Plugins
Marketplaces
Pricing
About
Contact

Resources

Learning Center
Blog
Weekly Digest
Claude Code Docs
Plugin Guide
Plugin Reference
Plugin Marketplaces

Community

Browse on GitHub
Get Support

Legal

Terms of Service
Privacy Policy

Browse · Plugins · Top Plugins · Marketplaces · Components · Technologies · Skills · Agents · Commands · Hooks · MCP Servers · LSP Servers · Output Styles · Themes · Monitors

Categories · Productivity · Development · Testing · Deployment · Security · Documentation · Data · Utilities

© 2025 ClaudePluginHub

Community Maintained · Not affiliated with Anthropic

ClaudePluginHub

ClaudePluginHub

Tools Learn Pricing

Search everything...

root-cause-analysis | debugging

Home
Skills
debugging
root-cause-analysis

Skill

root-cause-analysis

Five Whys, fishbone diagrams, identifying systemic causes not just symptoms.

Popularity

Parent stars

13

Parent forks

2

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/debugging:root-cause-analysis

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Finding the true cause of problems, not just surface symptoms.

SKILL.md

42 lines · ~358 tokens

Stats

Parent stars13

Parent forks2

MaintenanceFair

Last CommitMar 11, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Parent stars13

Parent forks2

MaintenanceFair

Last CommitMar 11, 2026

Actions

View Source View Plugin View on GitHub View README

Root Cause Analysis

Finding the true cause of problems, not just surface symptoms.

Context

You are helping identify root causes. Use 5 Whys or fishbone to dig deeper.

Domain Context

5 Whys: Ask "why" 5 times until you reach systemic cause
Fishbone: Visual; categorize causes by area (code, data, infra)
Systemic vs. Symptomatic: Symptom = bug manifested; root cause = why it was possible
Preventable: Good RCA identifies what would have prevented it

Instructions

Identify Symptom: What failed? What did users see?
Ask Why: Why did that happen?
Repeat: Ask why 4 more times; each answer becomes new "why"
Categorize: Use fishbone: Code, Data, Infrastructure, People?
Identify Root: Most fundamental cause; fixing it prevents recurrence
Verify: Would fixing root cause prevent this bug?

Anti-Patterns

Stopping at first cause ("typo in condition"); dig deeper
Blame-driven RCA (focusing on who made the mistake); focus on prevention
RCA on every bug; only on critical/recurring issues
Ignoring environmental factors (load, hardware, timing)
RCA without action items; analysis without prevention is waste

Further Reading

The Art of Systems Thinking (Daniel H. Kim)
Blameless postmortems from Google SRE

$

npx claudepluginhub sethdford/claude-skills --plugin engineer-debugging

Similar Skills

five-whys

12

Iterates 'why?' to uncover systemic root causes rather than surface symptoms. Useful for incident post-mortems, debugging sessions, and process improvement.

use-context-root-cause-analysis

10

Diagnoses root causes of failures using the 5 Whys technique, distinguishing isolated, recurring, or systematic issues.

2 files4 tools

View use-context-root-cause-analysis

apply-five-whys

12

Investigates root causes of defects or incidents by iteratively asking 'why' to trace failures from symptoms to systemic causes. Useful for postmortems and recurring failures.

View apply-five-whys