What problem does it solve? When tests fail, builds break, or behavior stops matching expectations, developers often guess at fixes or patch symptoms instead of causes. This Skill enforces a systematic stop-the-line debugging process that preserves evidence, localizes failures, and fixes root causes with regression tests. ## Core Features & Use Cases - Six-Step Triage Checklist: Reproduce, localize, reduce, fix the root cause, guard against recurrence, and verify end-to-end. - Error-Specific Decision Trees: Structured triage flows for test failures, build failures, runtime errors, and non-reproducible bugs including timing, environment, and state-dependent issues. - Regression Guardrails: Guidance on writing tests that fail without the fix, using git bisect for regressions, and safe fallback patterns under time pressure. - Use Case: A test suite fails after a refactor. Instead of guessing, you follow the checklist to reproduce the failure in isolation, bisect to the offending commit, fix the underlying query bug, and add a regression test before resuming feature work. ## Quick Start Use the debugging-and-error-recovery skill to triage this failing test and find the root cause before fixing it.