Drives root-cause analysis by iteratively questioning why and updating AGENTS.md.
npx skills add https://github.com/dmooney/Rundale --skill five-whys-dmooney
Please help me install this Agent Skill. Skill: five-whys Source: https://github.com/dmooney/Rundale/tree/main/.agents/skills/five-whys Command: npx skills add https://github.com/dmooney/Rundale --skill five-whys-dmooney
Five Whys helps you stop chasing symptoms by drilling into the underlying cause of a bug, regression, incident, or unexpected behavior until the true driver is found.
Use when you’re investigating a failing test, a regression after an update, a CI/incident mystery, or any behavior that surprises users and can’t be resolved confidently without understanding why it happens.
Use the five-whys approach to analyze a specific issue by stating the exact observed problem, answering each "why?" with a verifiable fact, and continuing for about five iterations until you identify the root cause and the prevention change needed in AGENTS.md.
High-intent search queries and answers about installing and using this skill.
Root cause analysis for test failures and regressions is found by iteratively asking "why" until the underlying issue is identified. Each answer must be an evidence-based fact from logs or code, preventing you from merely treating symptoms instead of the actual failure mechanism.
Incident review requires evidence-based root cause analysis, repeatedly questioning why the issue occurred until the true driver is found. This disciplined approach stops you from fixing surface effects and ensures the actual failure mechanism is addressed before resolution.
Evidence-based debugging involves asking "why" repeatedly, demanding verifiable facts from logs, tests, or measurements for each answer. This prevents assumptions from corrupting your root cause analysis when investigating unexpected behavior or CI mysteries.
Preventing recurring bugs requires updating AGENTS.md with missing rules, enforcement, or test coverage identified during root cause analysis. This final prevention step ensures the systemic gap that allowed the failure is closed alongside the immediate fix.
You should stop asking why during root cause analysis when a disciplined stop condition is met, typically after about five iterations. The process concludes once you identify the underlying cause and the specific prevention change needed in AGENTS.md.
vobbilisReproduce nexus-db errors from logs and verify X-Scope-OrgID headers.
ROYIANSAnalyze resolved software bugs to classify root causes and plan prevention mechanisms.
richardmbaileyDiagnose software defects through reproducible experimentation and automated verification tests.
klenGuide iterative Five Whys questioning to identify systemic root causes.
