What problem does it solve? Developers often jump straight to patching symptoms, which leads to recurring bugs, layered hacks, and wasted effort. This Skill enforces a disciplined four-phase debugging methodology that finds the actual root cause before any fix is written. ## Core Features & Use Cases - Root Cause Investigation: Read error messages fully, build a tight red/green feedback loop, check recent changes, and trace data flow to its origin. - Hypothesis-Driven Testing: Form 3-5 ranked falsifiable hypotheses, test one variable at a time, and verify with a minimal reproduction before implementing anything. - Regression-First Fixes: Write a failing regression test before the fix, apply a single root-cause change, and escalate to architectural review after three failed attempts. - Use Case: A flaky test fails intermittently in CI. Use this Skill to raise the reproduction rate, isolate the failing component boundary, form ranked hypotheses, and land a verified fix with a regression test. ## Quick Start Use the systematic-debugging skill to investigate why the login endpoint returns a 500 error before proposing any fix.
