skills/analyzing-root-causes/SKILL.md
Root cause analysis with 5 Whys. Use when: root cause, 5 Whys, なぜなぜ分析, 根本原因, 原因分析, symptom fix, 対症療法.
npx skillsauth add thkt/dotclaude analyzing-root-causesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Type | Example | Result | | ----------- | -------------------------- | ------------- | | Symptom Fix | setTimeout to wait for DOM | Breaks later | | Root Cause | Use React ref properly | Permanent fix | | Symptom Fix | Add flag for double-submit | Complexity ↑ | | Root Cause | Disable button on submit | Simple fix |
| Step | Question | Reveals | | ---- | ----------------------------- | ------------------------ | | 1 | Why does this occur? | Observable fact | | 2 | Why does that happen? | Implementation detail | | 3 | Why is that the case? | Design decision | | 4 | Why does that exist? | Architectural constraint | | 5 | Why was it designed this way? | Root cause |
| Topic | File |
| -------- | ---------------------------------------------------- |
| 5 Whys | ${CLAUDE_SKILL_DIR}/references/five-whys.md |
| Patterns | ${CLAUDE_SKILL_DIR}/references/symptom-patterns.md |
tools
Delegate implementation to codex (coder) via the herdr-agentchat plugin and drive a two-pane conversation to completion.
development
Extract recurring patterns from past closed PRs/issues and the research findings in workspace/research/, verify them against the latest code, and propose them to docs/wiki/ via PR.
development
Create Decision Records (DR) in MADR v4 format with auto-numbering.
development
Detect flaky tests by shaking them — repeated runs under varied order, parallelism, and seed — plus a static smell scan that flags latent flakiness in tests that currently pass. Classify each target as confirmed-flaky, latent-flaky, or stable and fix the root cause without weakening the test. Do NOT use to fix a confirmed single bug (use /fix) or for static-only code review (use /audit).