skills.rest
DavidEdeni
DavidEdeniCOMMUNITY
Explore all skills by this author →
GitHub

debugging-and-error-recovery

Identify and fix root causes of software failures through a systematic reproduce-to-verify workflow.

1|Updated Apr 12, 2026
Search Tags:#debugging#reproduce#triage#root-cause#incident-management#build-failure
One-click install
npx skills add https://github.com/DavidEdeni/web-development-tools --skill debugging-and-error-recovery-davidedeni
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/DavidEdeni/web-development-tools/tree/main/agent-skills/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/DavidEdeni/web-development-tools --skill debugging-and-error-recovery-davidedeni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging can be time-consuming and error-prone when tests fail, builds break, or behavior diverges; this Skill provides a structured approach to find and fix root causes instead of guessing.

Core Features & Use Cases

  • Stepwise triage to reproduce, localize, reduce, fix, and verify issues across tests, builds, runtimes, and incidents
  • Guidance for evidence preservation, instrumentation, and guardrails to prevent recurrence
  • Real-world scenario coverage from initial detection to verified resolution

Quick Start

Start by reproducing the failure, then follow the triage checklist to identify and fix the root cause and verify the fix.

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 build failure or runtime bug?▼

Systematic debugging finds root causes in build failures and runtime bugs by guiding you through reproduce, localize, reduce, fix, guard, and verify stages. This structured workflow replaces guessing with evidence-based triage.

What is the best way to triage a production incident?▼

Triaging a production incident requires a stepwise debugging checklist that preserves evidence and applies instrumentation. It guides you from initial detection through localization to a verified resolution while preventing recurrence.

Can I use a systematic debugging workflow for test failures?▼

Yes, systematic debugging workflows apply directly to test failures. They guide you through reproducing the failure, localizing the fault, reducing the test case, applying a fix, adding guardrails, and verifying the resolution.

How do I prevent recurring software bugs after deploying a fix?▼

To prevent recurring software bugs, the debugging workflow includes dedicated guard and verify stages. These steps enforce guardrails and validation to ensure the root cause is resolved and the failure does not happen again.

Does systematic debugging require specific dependencies or components?▼

Systematic debugging requires no specific dependencies or components. The workflow enforces structural requirements like frontmatter validation and optionally supports resources in scripts, references, and assets for evidence preservation.

Related Skills

Explore More Software Engineering Skills→
mopeyjellyfishmopeyjellyfish
1

debug

Reproduce bugs from evidence and prove root causes with red signals.

Community
Advanced
BorisserzBorisserz
1

debugging-and-error-recovery

Diagnose and fix root causes of test failures, build breaks, and runtime bugs.

Community
Advanced
logo-solutionslogo-solutions

debugging-and-error-recovery

Guide systematic root-cause debugging of failing tests and build errors.

Official
Advanced
T1nker-1220T1nker-1220

debugging-systematic

Diagnose software issues through root-cause analysis with hypotheses and logging.

Community
Intermediate