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 debugging process that preserves evidence, localizes failures, and produces verified fixes with regression tests. ## Core Features & Use Cases - Six-Step Triage Checklist: Reproduce, localize, reduce, fix the root cause, guard against recurrence, and verify end-to-end, with decision trees for each step. - Error-Specific Patterns: Dedicated triage flows for test failures, build failures, and runtime errors, plus strategies for non-reproducible timing, environment, and state-dependent bugs. - Safe Fallbacks and Instrumentation: Guidance on graceful degradation, defensive defaults, and when to add or remove logging during diagnosis. - Use Case: A test suite fails after a refactor. Instead of guessing, you follow the checklist to reproduce the failure, bisect the offending commit with git bisect, reduce to a minimal case, fix the actual cause, and add a regression test. ## 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.
