debugging-and-error-recovery

Debug failing tests and build errors by following a structured triage checklist to reproduce reliably, localize the fault, create a minimal repro, fix the root cause, and verify end-to-end. This evidence-first approach prevents guessing and avoids regressions.

The best way to find a regression commit is using git bisect. This Skill guides you through git bisect to systematically narrow down commits, localizing the exact change that introduced the defect so you can target the root cause directly.

Fix flaky tests by reproducing the failure reliably and localizing the fault through targeted instrumentation and logging. After applying the root-cause fix, add regression-test guardrails to verify the behavior and prevent future recurrence.

Yes, you can use this systematic debugging process for production incident response. It applies a stop-the-line triage method: preserve evidence, reproduce the issue, minimize the repro, fix the root cause, and verify the resolution before resuming work.

When a runtime bug is hard to reproduce, follow the triage steps to preserve evidence and add targeted instrumentation. Creating a minimal repro helps isolate the exact conditions triggering the unexpected behavior for accurate root-cause analysis.