debugging-and-error-recovery

Diagnose software failure root causes and apply verified recovery workflows.

Updated Jun 18, 2026

Search Tags:#testing #software engineering #debugging #root cause analysis #regression #error recovery

Ready to run

npx skills add https://github.com/MinhDuyDEV/mdpi --skill debugging-and-error-recovery-minhduydev

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents random debugging attempts by guiding agents through evidence-based failure diagnosis, root-cause analysis, safe fixes, and verification.

Core Features & Use Cases

Structured Failure Triage: Reproduce issues, preserve evidence, localize failures, reduce cases, and identify underlying causes before changing code.
Safe Recovery Workflow: Apply guarded fixes, add regression protection, verify outcomes, and escalate when assumptions or architecture are at risk.
Use Case: When a build, test suite, or runtime behavior breaks after a change, use this Skill to investigate the failure systematically and restore a verified working state.

Quick Start

Use the debugging-and-error-recovery skill to investigate the failing test, identify the root cause, and provide a verified fix plan.

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 suite by finding the root cause?▼

Debug a failing test suite by reproducing the issue, preserving evidence, localizing the fault, and reducing the case to identify the root cause before applying a safe fix.

What is the best way to recover from a broken build after a code change?▼

The best way to recover from a broken build is to follow a systematic recovery workflow that applies guarded fixes, adds regression protection, and performs end-to-end verification.

How do I fix a runtime error without random code changes?▼

Fix runtime errors through evidence-based diagnosis that collects failure data, localizes the fault, and verifies the outcome rather than attempting random debugging changes.

Does this systematic debugging approach work for unexpected regressions across different environments?▼

Yes, this approach applies to diagnosing regressions and unexpected system behavior across development environments by requiring evidence collection, fault localization, and regression safeguards.

When should I escalate a software failure during error recovery?▼

Escalate a software failure during error recovery when your assumptions are at risk or the underlying architecture is compromised beyond the scope of guarded fixes.

Why do I need to verify outcomes after applying a recovery fix?▼

You need to verify outcomes after applying a recovery fix to ensure the root cause is resolved and to restore a verified working state with end-to-end verification practices.