What problem does it solve? When tests fail, builds break, or runtime behavior goes wrong, developers often guess at fixes or push past errors, wasting hours and compounding bugs. This Skill enforces a structured stop-the-line process that preserves evidence, localizes the failure, and fixes the actual root cause instead of symptoms. ## Core Features & Use Cases - Six-Step Triage Checklist: Reproduce, localize, reduce, fix the root cause, guard with a regression test, and verify end-to-end. - Error-Specific Decision Trees: Structured triage flows for test failures, build failures, runtime errors, and non-reproducible bugs (timing, environment, or state dependent). - Bisection and Instrumentation Guidance: Use git bisect to find regression-introducing commits and apply temporary logging only when it aids diagnosis. - Use Case: A test suite fails after a refactor. Instead of guessing, you reproduce the failure in isolation, bisect to the offending commit, reduce to a minimal case, fix the underlying query bug, and add a regression test that fails without the fix. ## Quick Start Use the debugging-and-error-recovery skill to triage this failing test and find its root cause before fixing it.
