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, localizes the failure, and fixes the actual cause. ## Core Features & Use Cases - Structured Triage Checklist: A six-step process covering reproduce, localize, reduce, fix root cause, guard against recurrence, and verify end-to-end. - Error-Specific Decision Trees: Dedicated triage flows for test failures, build failures, runtime errors, and non-reproducible bugs including timing, environment, and state-dependent issues. - Regression Guarding: Guidance on writing tests that fail without the fix, plus safe fallback patterns and instrumentation rules. - Use Case: A CI build breaks after a merge. Instead of guessing, you follow the checklist: reproduce locally, bisect with git to find the offending commit, reduce to a minimal failing 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 fixing it.
