What problem does it solve? When tests fail, builds break, or runtime behavior diverges from expectations, developers often guess at fixes, patch symptoms, or push past errors — compounding bugs and wasting hours. This Skill enforces a disciplined, evidence-first debugging process that finds and fixes the actual root cause. ## Core Features & Use Cases - Structured Triage Checklist: A six-step ordered process — Reproduce, Localize, Reduce, Fix Root Cause, Guard, Verify — with explicit gates for Expected-vs-Actual, Why-Now, and Blast Radius analysis before any code change. - Error-Specific Decision Trees: Branching triage flows for test failures, build failures (type, import, config, dependency, environment), and runtime errors (NPEs, network errors, Compose crashes), plus strategies for non-reproducible and flaky bugs. - Regression Guarding & Safe Fallbacks: Guidance on writing regression tests that fail without the fix, safe fallback patterns in Kotlin (graceful degradation, safe defaults), and instrumentation rules for when to add or remove logging. - Use Case: A Gradle test suite fails after a refactor. Instead of guessing, you follow the checklist: reproduce the failure with ./gradlew test --tests, bisect with git bisect to find the offending commit, state the root cause and fix proposal, apply the minimal fix, 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 changing any code.
