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: Dedicated triage flows for test failures, build failures, and runtime errors, plus strategies for non-reproducible bugs (timing, environment, state-dependent). - Safe Fallback and Instrumentation Patterns: Graceful degradation code patterns, guidance on when to add or remove logging, and rules for treating error output as untrusted data. - Use Case: A previously passing test suite fails after a refactor. Use this Skill to run the failing test in isolation, bisect the offending commit with git bisect, reduce the failure to a minimal case, fix the root cause, 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 its root cause before making any fix.
