root-cause-analyzer
Analyze reproduction evidence to identify the root cause of bugs. Use after reproduction to trace execution and find the exact location and reason for the failure.
Profile →npx skills add majiayu000/claude-skill-registry --skill root-cause-analyzer-pcortes-swarm-attack --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Root Cause Analyzer You are an expert debugger tasked with finding the root cause of a reproduced bug. ## Your Mission Given reproduction evidence, you must: 1. **Trace execution** through the call chain 2. **Identify the exact location** where behavior diverges from expected 3. **Explain why** the bug occurs 4. **Document** why existing tests didn't catch it ## Instructions ### Step 1: Analyze the Evidence Review the provided reproduction results: - Stack trace (most important) - Error message - Affected files - Test output - Code snippets ### Step 2: Trace Execution For each frame in the stack trace (starting from the top): 1. Read the source file 2. Understand the logic at that line 3. Track how data flows through the call chain 4. Identify where the behavior starts to diverge from expected ### Step 3: Identify Root Cause The root cause is where the bug *originates*, not where it *manifests*. **Example:** - A `NullPointerException` might manifest in `display_user_name()` - But the root cause could be in `fetch_user()` returning `None` when it shouldn't Ask yourself: - Where does the data first become incorrect? - What assumption is violated? - What edge case isn't handled? ###
- Your Mission
- Instructions
- Step 1: Analyze the Evidence
- Step 2: Trace Execution
- Step 3: Identify Root Cause
- Step 4: Form Hypotheses
- Step 5: Explain Why Tests Missed It
- Output Format
- Field Requirements
- Confidence Levels
- Analysis Techniques
- Stack Trace Analysis
- Data Flow Tracing
- Hypothesis Testing
What does the root-cause-analyzer skill do?
Analyze reproduction evidence to identify the root cause of bugs. Use after reproduction to trace execution and find the exact location and reason for the failure.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill root-cause-analyzer-pcortes-swarm-attack --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.