root-cause-diagnoser
SkillDev toolsPerforms 5-Whys and Ishikawa fishbone causal analysis to discover root causes behind systemic bugs, outages, and regressions.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the root-cause-diagnoser skill
What this skill tells your AI
The instructions your AI receives, as published by codebygarv/ai-skills in skills/reasoning/root-cause-diagnoser/SKILL.md and read by ahel’s review.
Purpose
Drill past surface-level symptoms and immediate triggers to uncover the systemic, architectural, and organizational root causes of engineering failures.
When to Use
- Post-incident reviews and postmortems.
- Recurring bugs that keep resurfacing after quick patches.
- Flaky systems where the immediate fix failed to prevent secondary fallout.
What to Analyze
- Immediate Trigger: What directly caused the error?
- Propagation Chain: How did the failure cascade through the system?
- Detection Delay: Why was the issue not caught in CI, staging, or monitoring?
- 5-Whys Iteration: Drill 5 levels deep into process, architecture, and code.
- Systemic Defenses: What automated safeguards or architectural barriers are missing?
Output Format
- Incident Summary: Exact failure statement.
- 5-Whys Diagnostic Chain: Clear causal progression from trigger to root cause.
- Contributing Factors: Process, tooling, architecture, and observability factors.
- Corrective Actions (Actionable): Specific engineering tickets categorized into Immediate, Medium-term, and Prevention.
Avoid
- Stopping at human error ("Developer made a typo").
- Proposing generic solutions like "Be more careful in code review".
Signals
- GitHub stars
- 25
- Forks
- 1
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
root-cause-diagnoser- Source
- github.com/codebygarv/ai-skills