analysis-diagnose
Perform systematic root cause investigation through 4-phase process. Use when encountering bugs, test failures, or unexpected behavior. Includes evidence gathering, hypothesis formation, testing protocols, and solution justification. Not for trivial fixes, creative experimentation, learning new systems, or implementing solutions.
npx skills add majiayu000/claude-skill-registry --skill analysis-diagnose --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.
<mission_control> <objective>Perform systematic root cause investigation through evidence gathering, hypothesis formation, testing, and solution justification.</objective> <success_criteria> - Symptom documented with exact error messages and reproduction steps - Evidence gathered: logs, git history, environment data, diagnostics - Single hypothesis formed based on evidence (not assumptions) - Minimal reproduction test created to verify hypothesis - Root cause identified with file:line evidence - Fix strategy documented with verification approach </success_criteria> <semantic_anchors> - **Single Hypothesis**: Test one theory at a time for clear verification - **5 Whys**: Iterative "why" questioning to reach actionable root cause - **Pattern Recognition**: 3+ failures indicate systemic vs isolated issue - **Evidence-Based**: All claims require file reads or diagnostic output </semantic_anchors> </mission_control> ## Quick Start Bug encountered → Document symptom → Gather evidence → Form single hypothesis → Test with minimal reproduction → Identify root cause → Implement fix ## Navigation | If you need... | Read this section... | | :--- | :--- | | Run diagnosis | ## Quick Start | | 4-
- Quick Start
- Navigation
- Semantic Anchors
- Single Hypothesis Protocol
- 5 Whys Technique
- Pattern Recognition
- Evidence-Based Investigation
- Diagnostic Flow
- Phase 1: State the Problem
- Phase 2: Gather Evidence
- Phase 3: Form Hypothesis
- Phase 4: Test & Conclude
- Investigation Format
- Troubleshooting
What does the analysis-diagnose skill do?
Perform systematic root cause investigation through 4-phase process. Use when encountering bugs, test failures, or unexpected behavior. Includes evidence gathering, hypothesis formation, testing protocols, and solution justification. Not for trivial fixes, creative experimentation, learning new systems, or implementing solutions.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill analysis-diagnose --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.