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 workflow that preserves evidence, reproduces the failure, and fixes the actual cause. ## 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). - Safe Fallback and Instrumentation Patterns: Guidance on graceful degradation, safe defaults, and when to add or remove diagnostic logging. - Use Case: A test suite fails after a refactor. Instead of guessing, you follow the checklist: reproduce the failure in isolation, use git bisect to find the offending commit, fix the root cause, 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.
