debugging-and-error-recovery

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

Updated Jul 10, 2026

Search Tags:#debugging #troubleshooting #root cause analysis #regression testing #git bisect #test failure #error triage

Ready to run

npx skills add https://github.com/CodeCrafterAdi2006/Ink-and-Code --skill debugging-and-error-recovery-codecrafteradi2006

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/CodeCrafterAdi2006/Ink-and-Code/tree/main/Skills/debugging-and-error-recovery
Command: npx skills add https://github.com/CodeCrafterAdi2006/Ink-and-Code --skill debugging-and-error-recovery-codecrafteradi2006

SYSTEM DOCUMENTATION & REQUIREMENTS

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 workflow that preserves evidence, localizes the failure, and fixes the actual cause. ## Core Features & Use Cases - Six-Step Triage Checklist: Reproduce, localize, reduce, fix the root cause, guard with a regression test, and verify end-to-end. - Error-Specific Decision Trees: Dedicated triage flows for test failures, build failures, runtime errors, and non-reproducible bugs (timing, environment, or state dependent). - Safe Fallback & Instrumentation Patterns: Guidance on graceful degradation, safe defaults, and when to add or remove diagnostic logging. - Use Case: A CI build fails after a dependency update. Follow the checklist to reproduce locally, use git bisect to find the offending commit, fix the root cause, and add a regression test before resuming feature work. ## Quick Start Ask the assistant to systematically debug a failing test or broken build using the root-cause triage checklist instead of guessing at fixes.

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?▼

Reproduce the failure reliably first, then localize which layer is failing, reduce to a minimal failing case, and fix the root cause rather than the symptom. Finish by adding a regression test that fails without the fix and running the full suite to check for regressions.

How to find which commit introduced a bug?▼

Use git bisect: mark the current commit as bad and a known working commit as good, then test each midpoint checkout. You can automate it with git bisect run followed by your test command to identify the exact offending commit.

What should I do when a bug cannot be reproduced?▼

Determine whether it is timing, environment, or state dependent. Add timestamps and logging around the suspected area, compare environments and data states, try reproducing under load or in CI, and set up alerts for the error signature if it remains intermittent.

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

Symptom fixes mask the underlying defect, so the bug resurfaces elsewhere and compounds with later changes. Asking why the failure happens until reaching the actual cause ensures the fix is durable and the regression test is meaningful.

When should I add or remove debug logging?▼

Add instrumentation when you cannot localize a failure or the issue is intermittent, and remove it once the bug is fixed and guarded by tests. Keep permanent logging only for error boundaries, API error context, and key performance metrics.