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. This Skill enforces a disciplined stop-the-line workflow that preserves evidence, reproduces the failure, and fixes the actual cause before work resumes. ## 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 paths for test failures, build failures, runtime errors, and non-reproducible bugs including timing, environment, and state-dependent issues. - Safe Fallback Patterns: Graceful degradation and safe-default code patterns for handling failures under time pressure, plus guidance on when to add or remove instrumentation. - Use Case: A test suite fails after a refactor. Instead of guessing, follow the checklist to 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 skill to triage why the login test started failing after my last commit and fix the root cause.
