eng-debug-rca

What problem does it solve?

This Skill converts ad-hoc debugging into a structured, evidence-driven root cause analysis process that reduces time-to-resolution, prevents misdirected fixes, and ensures verifiable remediation by enforcing reproduction, hypothesis ranking, and documented verification.

Core Features & Use Cases

• Hypothesis-driven workflow: Generate 3–7 ranked hypotheses before reading code, define evidence needs, and prioritize investigations by probability, confidence, and test cost.
• Investigation & tooling: Guided bisection for code regressions, reproduction gating, iterative testing (midthink), and an evidence board to mark hypotheses as confirmed or eliminated.
• Fix and documentation: Propose quick vs proper fixes with risks, verify against original repro steps, test adjacent functionality, save a local bug report, and log a one-line summary to memory. Use case: reproduce a production crash, run git bisection to find the offending commit, validate the root cause, and produce a compliant fix and local bug record.

Quick Start

Start an RCA by providing a concise bug description along with the repository path and logs path to initiate the hypothesis-driven debugging workflow.