debugging-and-error-recovery

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). - Bisection and Instrumentation Guidance: Use git bisect to find regressions and apply temporary logging with clear rules for when to add and remove it. - 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 shared-state leak causing it, and add a regression test before resuming work. ## Quick Start Ask the agent to systematically debug the failing test or broken build using the root-cause triage checklist instead of guessing at a fix.