What problem does it solve?
Debugging often stalls when developers jump to the first plausible explanation instead of working from evidence. This Skill provides a disciplined decision process for code failures, regressions, crashes, flaky behavior, and bad output: characterize the failure, bound the fault, rank falsifiable hypotheses, fix the smallest root cause, and prove the failing path.
Core Features & Use Cases
- Evidence-First Characterization: Captures exact symptoms, reproduction steps, stack traces, and determinism properties before theorizing, with explicit handling for cases where reproduction is unsafe or impossible.
- Hypothesis Ranking: Keeps one or two active hypotheses, each with a disproving observation and the cheapest discriminating check, preventing shotgun debugging.
- Root-Cause Fixing with Proof: Patches the smallest ownership boundary, stops after two failed fix attempts to re-challenge assumptions, and requires a regression check that would have failed before the fix.
- Use Case: A test fails intermittently in CI. Use this Skill to characterize the timing sensitivity, bound the fault across async and concurrency boundaries, run the cheapest discriminating check, fix the root cause, and add a focused regression test.
Quick Start
Ask the agent to debug an intermittent test failure by finding and fixing the root cause from the failing logs.