What problem does it solve? When a test fails, a build breaks, or runtime behavior diverges from expectations, developers often patch symptoms instead of root causes or push past failures and compound errors. This Skill enforces a disciplined stop-the-line workflow that preserves evidence, localizes the failure, fixes the root cause, and guards against recurrence. ## Core Features & Use Cases - Six-Step Triage Checklist: Reproduce, localize, reduce, fix the root cause, add a regression test, and verify end-to-end, with decision trees for each step. - Error-Specific Triage Patterns: Dedicated decision trees for test failures, build failures, and runtime errors, plus git bisect guidance for regression hunting. - Safe Fallbacks and Instrumentation: Patterns for graceful degradation, safe config defaults, and rules for when to add or remove diagnostic logging. - Use Case: A test suite fails after a refactor. Follow the checklist to reproduce the failure in isolation, bisect to the offending commit, reduce to a minimal case, fix the underlying cause, and add a regression test that fails without the fix. ## Quick Start Use the debugging-and-error-recovery skill to triage this failing test and identify the root cause before fixing it.
