debugging-and-error-recovery

Diagnose software failures with a structured triage framework for root cause analysis.

1|1|Updated Apr 16, 2026

Search Tags:#debugging #triage #root-cause #bug-fix #incident-management #build-error #test-failure

Ready to run

npx skills add https://github.com/iCesofT/awesome-ai --skill debugging-and-error-recovery-icesoft

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/iCesofT/awesome-ai/tree/main/skills/04-testing-debugging-and-error-recovery
Command: npx skills add https://github.com/iCesofT/awesome-ai --skill debugging-and-error-recovery-icesoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps engineers diagnose failures and incidents by following a structured triage process instead of guesswork. It emphasizes preserving evidence, reproducing failures, and diagnosing root causes to prevent recurrence.

Core Features & Use Cases

Stop-the-Line Rule: halt feature work to preserve context and prevent cascading failures.
Triage Checklist: structured steps to reproduce, localize, reduce, fix, and guard against recurrence.
End-to-end verification: ensure fixes pass tests/builds and verify remediation in production-like conditions.
Use Case: when a test fails after a change, or logs show an unreproducible error; apply triage to determine root cause before implementing a fix.

Quick Start

Describe the failure, reproduce it, and apply the triage steps to locate and fix the root cause before resuming work.

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 find the root cause of a test failure or build error?▼

Find the root cause of a test failure or build error by applying a structured triage checklist. This enforces evidence preservation, reproduction steps, and localization to diagnose failures systematically instead of guesswork.

What is the best way to debug unreproducible runtime bugs from production logs?▼

Debug unreproducible runtime bugs by preserving evidence and enforcing strict reproduction steps. A disciplined triage framework helps localize the fault from production logs before any code changes are implemented.

How do I manage production incidents and prevent bug recurrence?▼

Manage production incidents and prevent bug recurrence by applying a triage process that localizes the fault, implements a fix, and adds guards. End-to-end verification ensures remediation works in production-like conditions.

Why should I stop feature work when a software incident occurs?▼

Stop feature work during a software incident to preserve context and prevent cascading failures. This stop-the-line rule halts new changes, ensuring evidence is intact for accurate root-cause debugging.

Can I use a systematic triage checklist for any software project failure?▼

Yes, you can use a systematic triage checklist for any software project failure. It applies across software teams to test failures, build errors, runtime bugs, and production incidents without requiring specific dependencies.