root-cause-analysis

Diagnose underlying causes of bugs and failures using systematic investigation techniques.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/fabioc-aloha/AlexAgent --skill root-cause-analysis-fabioc-aloha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: root-cause-analysis
Source: https://github.com/fabioc-aloha/AlexAgent/tree/main/plugin/skills/root-cause-analysis
Command: npx skills add https://github.com/fabioc-aloha/AlexAgent --skill root-cause-analysis-fabioc-aloha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fixes that only address symptoms let the same bug return. This Skill guides systematic debugging from observed symptoms down to preventable root causes, so issues are resolved permanently instead of patched temporarily. ## Core Features & Use Cases - 5 Whys Analysis: Structured questioning chains with evidence requirements and common traps to avoid, such as stopping at human error or speculating without proof. - Investigation Techniques: Binary search debugging with git bisect, timeline reconstruction from logs and deploys, and correlation-versus-causation confidence scoring. - Fix + Prevent Pattern: Three-phase remediation covering immediate mitigation, permanent root-cause fixes, and systemic prevention like CI checks and PR checklists. - Use Case: A production page crashes intermittently. Use this Skill to trace the TypeError back through a null API response, a database timeout, and a missing index, ultimately identifying a process gap in the PR review workflow and adding a performance checklist to prevent recurrence. ## Quick Start Use the root-cause-analysis skill to investigate why the production deploy keeps failing and identify the permanent fix.

Frequently Asked Questions about root-cause-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the root cause of a recurring bug?▼

Use the 5 Whys technique: ask why the symptom occurred, then keep asking why for each answer until you reach something preventable. Each answer must be backed by evidence from logs, tests, or metrics rather than speculation.

How to use git bisect for binary search debugging?▼

Identify the last known good commit and the first bad commit, then run git bisect to halve the search space. At each step, test whether the bug exists and narrow toward the exact commit that introduced it.

What is the difference between correlation and causation in debugging?▼

Correlation means two events happened together, while causation means one caused the other. On-demand reproduction gives high confidence, deploy correlation is medium, and timing coincidences or memory-based claims are low-confidence evidence.

Why do fixed bugs keep coming back?▼

Recurring bugs mean you fixed a symptom, not the root cause. Apply the fix-plus-prevent pattern: stop the bleeding immediately, implement a permanent fix, then add systemic prevention like CI checks, monitoring alerts, or PR checklists.

When should I stop asking why in a 5 Whys analysis?▼

Stop when you reach an actionable system change, such as a missing process or review step. Going too deep leads to unactionable answers, while stopping at human error misses the systemic gap that made the error possible.