debugging-and-error-recovery

Diagnose test failures, build errors, and runtime bugs through structured root-cause triage.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/MSC72m/DevForge --skill debugging-and-error-recovery-msc72m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/MSC72m/DevForge/tree/main/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/MSC72m/DevForge --skill debugging-and-error-recovery-msc72m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When tests fail, builds break, or behavior stops matching expectations, developers often guess at fixes or patch symptoms instead of causes. This Skill enforces a systematic stop-the-line debugging process that preserves evidence, localizes failures, and fixes root causes 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. - Error-Specific Decision Trees: Structured triage flows for test failures, build failures, runtime errors, and non-reproducible bugs including timing, environment, and state-dependent issues. - Regression Guardrails: Guidance on writing tests that fail without the fix, using git bisect for regressions, and safe fallback patterns under time pressure. - Use Case: A test suite fails after a refactor. Instead of guessing, you follow the checklist to reproduce the failure in isolation, bisect to the offending commit, fix the underlying query bug, 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 the root cause before fixing it.

Frequently Asked Questions about debugging-and-error-recovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a failing test systematically?▼

Debug a failing test by first reproducing it reliably, then localizing which layer fails, reducing to a minimal case, and fixing the root cause rather than the symptom. Finish by adding a regression test and verifying the full suite passes.

How to find which commit introduced a bug?▼

Use git bisect to find the commit that introduced a bug. Mark the current commit as bad and a known-working commit as good, then run your failing test at each midpoint checkout, optionally automating it with git bisect run.

What should I do when a bug is not reproducible?▼

For non-reproducible bugs, check whether the issue is timing-dependent, environment-dependent, or state-dependent. Add timestamps to logs, compare environments and data, check for leaked shared state, and set up monitoring for the error signature.

Why is fixing symptoms instead of root causes a problem?▼

Fixing symptoms masks the underlying defect, so the bug resurfaces elsewhere and later changes build on broken behavior. Asking why the failure happens until reaching the actual cause prevents recurring incidents and compounding errors.

When should I remove debug logging from code?▼

Remove temporary instrumentation once the bug is fixed and regression tests guard against recurrence, or when logs are only useful during development. Always remove logs containing sensitive data, but keep permanent error boundaries and API error logging.