debugging-and-error-recovery

Diagnose software defects through structured triaging and root cause analysis.

Updated Apr 19, 2026

Search Tags:#testing #debugging #troubleshooting #root cause analysis #software maintenance #error recovery

Ready to run

npx skills add https://github.com/dmarins/sdd --skill debugging-and-error-recovery-dmarins

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/dmarins/sdd/tree/main/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/dmarins/sdd --skill debugging-and-error-recovery-dmarins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates guesswork during troubleshooting by providing a rigorous, step-by-step framework to identify, isolate, and resolve the root cause of software failures, preventing superficial fixes and recurring bugs.

Core Features & Use Cases

Structured Triaging: A standardized checklist for handling test failures, build errors, and runtime exceptions.
Root Cause Analysis: Techniques like bisection and minimal reproduction to ensure fixes address the source of the problem rather than symptoms.
Use Case: When a production service experiences intermittent timeouts, use this skill to systematically isolate the failure point, verify the fix with a regression test, and document the lesson learned to prevent future occurrences.

Quick Start

Use the debugging and error recovery skill to perform a systematic root cause analysis on the failing test case in the current module.

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 perform a systematic root cause analysis for a runtime exception?▼

Systematic root cause analysis for a runtime exception involves structured triaging, isolating the failure point through minimal reproduction, and verifying the fix with a regression test. This framework ensures you resolve the source of the problem rather than just treating symptoms.

What is the best way to troubleshoot intermittent production service timeouts?▼

The best way to troubleshoot intermittent production service timeouts is to apply a standardized triaging workflow. This involves systematically isolating the failure point, verifying the specific fix with a regression test, and explicitly documenting the lesson learned to prevent future recurrences.

How do I stop recurring software bugs and prevent superficial fixes?▼

To stop recurring software bugs and prevent superficial fixes, use an evidence-based problem-solving framework. Techniques like bisection and minimal reproduction target the actual root cause of software failures, ensuring that the underlying defect is fully resolved rather than temporarily patched.

Can I use this debugging framework for both build errors and test failures?▼

Yes, you can use this debugging framework for both build errors and test failures. It provides a standardized checklist for structured triaging that applies directly to diagnosing and resolving various software defects, including build errors, runtime exceptions, and production incidents.

When do I need a structured triaging checklist for software maintenance?▼

You need a structured triaging checklist for software maintenance when you want to eliminate guesswork during troubleshooting. It provides a rigorous, step-by-step framework to identify, isolate, and resolve the root cause of software failures across test failures, build errors, and production incidents.

Does this error recovery framework require any specific dependencies?▼

No, this error recovery framework does not require any specific external dependencies or components. It is a self-contained, systematic reasoning framework designed to guide evidence-based problem solving and regression testing across any software maintenance environment.