debugging-and-error-recovery

Diagnose failing tests, build errors, and runtime issues with structured triage workflows.

Updated May 27, 2026

Search Tags:#debugging #root cause analysis #error recovery #test failure #bug triage #build error

Ready to run

npx skills add https://github.com/santanapol/agent-skills --skill debugging-and-error-recovery-santanapol

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates wasted time on random, guesswork-based bug fixes by providing a structured, systematic workflow for diagnosing and resolving failing tests, broken builds, unexpected runtime errors, and production incidents, preventing bug accumulation that causes cascading failures.

Core Features & Use Cases

Structured Triage Workflow: Enforces a stop-the-line process to preserve evidence, reproduce issues, localize fault layers, reduce to minimal reproducible cases, fix root causes, and add regression guards.
Error-Specific Playbooks: Includes tailored triage checklists for test failures, build errors, and runtime crashes, plus safe fallback patterns for high-pressure scenarios.
Use Case: When a previously passing test fails after a code change, or a production error appears without clear cause, use this Skill to avoid random fixes and resolve the issue permanently with verification steps.

Quick Start

Use the debugging-and-error-recovery skill to systematically diagnose and fix the failing test in the payment-processing 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 debug a failing test after a recent code change?▼

Debug a failing test by following a structured triage workflow that preserves evidence, reproduces the issue, localizes the fault layer, reduces it to a minimal case, fixes the root cause, and adds regression test guidelines to prevent recurrence.

What is the best way to resolve a broken build error without guessing?▼

Resolve a broken build error by applying error-specific triage checklists that systematically isolate the fault layer and apply safe fallback patterns, replacing random guesswork with verified root cause resolution.

How do I diagnose a runtime error or production incident systematically?▼

Diagnose a runtime error or production incident by executing a stop-the-line process that preserves evidence, localizes the unexpected error to its fault layer, and reduces it to a minimal reproducible case for root cause analysis.

Can I use a structured workflow for regression bug tracking and prevention?▼

Yes, use a structured bug triage workflow for regression bug tracking that enforces fault localization, root cause resolution, and the addition of regression test guidelines to permanently prevent bug accumulation and recurrence.

When should I use a safe fallback pattern during error recovery?▼

Use a safe fallback pattern during error recovery in high-pressure scenarios, such as unexpected production issues or runtime crashes, to stabilize the environment while systematically working through the root cause resolution workflow.