hoavdc/CodexKit / skills/codexkit-root-cause-analyzer
codexkit-root-cause-analyzer
VerifiedConduct structured root cause analysis using Ishikawa (Fishbone), 5 Whys, and Pareto methods. Suitable for production incidents, quality defects, customer complaints, and recurring operational problems. Use when problems recur or when initial fixes do not resolve the issue. Do not use for one-time, obvious fixes or strategic decision-making.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.9 KB |
| agents/openai.yaml | config | 168 B |
| examples/common-mistakes.md | markdown | 811 B |
| examples/good-output.md | markdown | 887 B |
| verification/checklist.md | markdown | 1.3 KB |
examples/common-mistakes.md
View on GitHub# Common Mistakes — Root Cause Analyzer
> Anti-patterns to watch for when using the Root Cause Analyzer skill.
## 1. Stopping at the human layer
**What goes wrong:** 'Root cause: engineer deployed without testing' — that's blame, not analysis
**How to fix it:** Ask: 'Why was it possible to deploy without testing?' Fix the system, not the person.
## 2. Single causal chain tunnel vision
**What goes wrong:** Following one 'Why' chain and missing alternative contributing factors
**How to fix it:** After the first chain, ask: 'What else contributed?' Use Fishbone for multi-factor problems.
## 3. Analysis without action
**What goes wrong:** Beautiful root cause diagram, zero action items with deadlines
**How to fix it:** Every root cause must produce ≥1 action item with owner and due date.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |