What problem does it solve? When tests fail, builds break, or runtime behavior goes wrong, developers often guess at fixes or patch symptoms instead of root causes, wasting hours and letting bugs compound. This Skill enforces a disciplined stop-the-line debugging process that preserves evidence, localizes the failure, and fixes the actual cause. ## Core Features & Use Cases - Structured Triage Checklist: A six-step ordered process (reproduce, localize, reduce, fix root cause, guard, verify) with decision trees for test failures, build errors, and runtime bugs. - Non-Reproducible Bug Strategies: Concrete tactics for timing-dependent, environment-dependent, and state-dependent failures, including git bisect workflows for regression hunting. - Regression Guarding & Safe Fallbacks: Patterns for writing regression tests, graceful degradation, safe config defaults, and instrumentation guidelines that distinguish temporary logging from permanent monitoring. - Use Case: A CI pipeline fails after a refactor. Instead of guessing, follow the triage checklist to reproduce locally, bisect to the offending commit, reduce to a minimal failing case, fix the root cause, and add a regression test before resuming feature work. ## Quick Start Ask the assistant to systematically debug the failing test or error you are seeing and find its root cause instead of guessing.
