investigatelisted

Deep root cause analysis engine for defects whose cause is genuinely unknown. Runs an 8-phase diagnostic protocol — observe, reproduce, trace, hypothesize, prove, root cause, fix, prevent — using sequential-thinking MCP, multi-pass code reading, git forensics, competing hypotheses, and the 5 Whys, proving the cause with evidence before any fix. Returns a proven root-cause report; the fix runs only after that diagnosis is approved. Use when the user runs /investigate, or when a bug, crash, exception, stack trace, regression, flaky or intermittent failure, data corruption, memory leak, or unexplained slowness needs its root cause found and nobody knows why. Expensive — do not select it when the cause is already known, for a typo, syntax, import or config mistake, for a feature request or refactor, for "what does this code do", or for applying a fix the user already chose; handle those directly. For a live production outage, route to incident-commander first and investigate after service is restored.
pfangueiro/claude-code-agents · ★ 6 · AI & Automation · score 79

Install: claude install-skill pfangueiro/claude-code-agents

# Investigate — Root Cause Analysis Engine Systematic deep investigation protocol. Finds the REAL cause, not the surface symptom. **Core principle:** Never fix what you don't understand. Every fix must trace to a proven root cause with evidence. ## Pre-Flight Gate Activation is decided by the frontmatter description alone — this file is read only AFTER the skill has been selected. Nothing here can prevent over-triggering, so this gate is a **post-selection redirect**, not a filter. **Before proceeding, check the ABORT and ROUTE OUT conditions below. If any holds, STOP, say in one line which one fired, and take the redirect instead of starting the 8-phase protocol.** Being invoked — including a literal `/investigate` or "find the root cause" — does NOT override an ABORT: the phrasing that selected this skill is not evidence the cause is unknown. - Run the 8-phase protocol only for a real bug / unexpected behavior whose root cause is UNKNOWN. - ABORT: a bug whose cause is already known (just fix it), a feature request, an obvious-cause config/syntax error, or anything not actually broken. - ROUTE OUT: a **live production outage** — service down, users impacted, an active incident — goes to **incident-commander FIRST**. Mitigate and restore service, then run `/investigate` for the root cause. An unknown cause does NOT admit an outage to this protocol: diagnosis-before-mitigation is paid for in downtime. ## Protocol Process every `/investigate` invocation through these 8