thkt/use-context-root-cause-analysis
skills/use-context-root-cause-analysis/SKILL.md
Root cause analysis with 5 Whys.
$ install --global
skillsauthnpx skillsauth add thkt/dotclaude use-context-root-cause-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 27, 2026, 3:29 AM137.5s3 files scanned
SKILL.md
- name:
- use-context-root-cause-analysis
- description:
- Root cause analysis with 5 Whys.
- when_to_use:
- root cause, 5 Whys, なぜなぜ分析, 根本原因, 原因分析, symptom fix, 対症療法
- allowed-tools:
- Read Task Bash(ugrep:*) Bash(bfs:*)
- context:
- fork
- background:
- false
- user-invocable:
- false
Root Cause Analysis - 5 Whys
Principle
Fix the root cause, not the symptom. Symptom fixes add complexity; root-cause fixes prevent recurrence.
5 Whys Process
Ask "why" five times, descending through abstraction levels.
| Step | Level | | ---- | ------------------------ | | 1 | Observable fact | | 2 | Implementation detail | | 3 | Design decision | | 4 | Architectural constraint | | 5 | Root cause |
Tips
| Tip | Description | | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- | | Stay factual | Evidence, not assumptions | | Don't stop early | First "why" is rarely root cause | | Don't go deep | Stop when actionable | | Validate | "Because [5], therefore [4]..." | | Verify fix | "Will this prevent the problem?" | | Watch complexity signals | When intermittent / multiple independent changes overlap / behavior unexplained, enumerate ≥3 cause-layer candidates before converging |
Output Format
| Field | Description | | ---------- | ---------------------------------------- | | Symptom | User-facing failure | | Root cause | Why the failure occurred (5 Whys result) | | Pattern | Isolated / Recurring / Systematic |
Pattern Enum
Consumers such as the /fix Non-obvious flow branch on the Pattern field to decide whether to apply defense-in-depth or escalate.
| Value | Meaning | | ---------- | ------------------------------------------------- | | Isolated | Single location, no recurrence path | | Recurring | Similar code exists nearby, recurrence possible | | Systematic | Design-rooted, architecture-level recurrence risk |
References
| Topic | File | | -------------------- | -------------------------------------------------- | | Worked examples | ${CLAUDE_SKILL_DIR}/references/five-whys.md | | Symptom → Root Cause | ${CLAUDE_SKILL_DIR}/references/symptom-patterns.md |
Related Skills
thkt/use-cli-herdr
tools
VerifiedTrustedCommunity
Delegate implementation to codex (coder) via the herdr-agentchat plugin and drive a two-pane conversation to completion.
11SKILL.mdUpdated Jul 27, 2026
thkt/scribe
development
VerifiedTrustedCommunity
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.
11SKILL.mdUpdated Jul 20, 2026
thkt/dr
development
VerifiedTrustedCommunity
Create Decision Records (DR) in MADR v4 format with auto-numbering.
11SKILL.mdUpdated Jul 15, 2026
thkt/shake
development
VerifiedTrustedCommunity
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).
11SKILL.mdUpdated Jul 13, 2026