What problem does it solve? Debugging often devolves into guesswork: developers jump to conclusions, fix symptoms instead of root causes, or blame users without evidence. This Skill enforces a disciplined, evidence-first investigation process so every conclusion traces back to verifiable proof. ## Core Features & Use Cases - Structured Investigation Process: A six-step workflow covering reproduction, evidence collection, hypothesis ranking, bisection, confirmation, and root-cause fixing. - Evidence Discipline Rules: Requires every conclusion to trace to specific verifiable evidence, maintains multiple competing hypotheses, and rejects correlation-as-causation reasoning. - Anti-Rationalization Guardrails: A built-in table of common excuses (e.g., "the stack trace is enough") paired with factual rebuttals to keep investigations honest. - Use Case: When a production service intermittently fails, use this Skill to reproduce the failure, gather logs and stack traces, bisect the codebase with git bisect, and confirm the true root cause before committing a fix. ## Quick Start Ask the agent to investigate and find the root cause of the failing test or bug you are seeing, following a reproduce-first evidence-based process.
