debugging-and-error-recovery

Guides root-cause debugging of software failures through a stepwise verification workflow.

Updated Aug 27, 2026

Search Tags:#debugging #troubleshooting #logs #triage #reproducibility #root-cause #incident-management

Ready to run

npx skills add https://github.com/hodinhtuankiet/screening-resume-recruitment --skill debugging-and-error-recovery-hodinhtuankiet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/hodinhtuankiet/screening-resume-recruitment/tree/main/.claude/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/hodinhtuankiet/screening-resume-recruitment --skill debugging-and-error-recovery-hodinhtuankiet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with structured triage to stop guessing and quickly locate root causes, preserving evidence for reliable fixes.

Core Features & Use Cases

Stepwise triage workflow for reproducing failures, localizing the issue, and validating fixes.
Stop-the-Line rules and a guided checklist to prevent escalation and regression.
Real-world incident support for tests, builds, runtime bugs, and production incidents.

Quick Start

Reproduce the failure, preserve logs and evidence, and follow the triage checklist to identify the root cause.

Frequently Asked Questions about debugging-and-error-recovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is the best way to systematically debug a runtime bug in a backend service?▼

Systematic debugging requires a stepwise triage workflow to reproduce failures, preserve logs, localize the issue, and validate fixes. It enforces a stop-the-line rule to prevent escalation and ensure reliable root-cause resolution for backend runtime bugs.

How do I triage production incidents to find the root cause?▼

Triage production incidents by first reproducing the failure and preserving evidence like logs. Follow a structured checklist to localize the issue stepwise and validate the fix, ensuring the root cause is identified without guessing.

Can I use systematic debugging for test failures and build breaks?▼

Yes, systematic debugging applies to test failures and build breaks by enforcing reproducibility and evidence preservation. It provides a stepwise verification workflow to localize the issue and validate fixes across UI, API, and backend services.

Why does software failure escalation happen and how can I prevent it?▼

Escalation happens when issues are patched without finding the root cause. Prevent it by applying a stop-the-line rule and a guided triage checklist to enforce evidence preservation and stepwise verification before validating fixes.

What are the limitations of debugging without preserving logs and evidence?▼

Debugging without preserving logs and evidence leads to guessing and regression. The limitation is an inability to guarantee reliable fixes, which a structured triage workflow with stepwise verification and reproducibility requirements is designed to overcome.

Does this debugging workflow support UI, API, and backend services?▼

Yes, this debugging workflow supports UI, API, and backend services. It applies systematic triage, reproducibility, and evidence preservation to resolve runtime bugs, test failures, build breaks, and production incidents across these environments.