debugging-and-error-recovery

Diagnose software failures with a stepwise triage checklist for root-cause fixes.

1|Updated Apr 8, 2026

Search Tags:#debugging #reproduce #triage #root-cause #bug-fix #failure-analysis #incident-response

Ready to run

npx skills add https://github.com/pko89403/ZeroAlign-Rec --skill debugging-and-error-recovery-pko89403

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps engineering teams systematically diagnose failures without guessing, preserving evidence and reducing mean time to recovery (MTTR).

Core Features & Use Cases

Stop-the-Line triage: immediately halt feature work to diagnose failures and stabilize systems.
Reproducibility and localization: reproduce issues locally, isolate faulty components, and trace failure origins.
Guided remediation: follow a stepwise process (reproduce, localize, reduce, fix, verify) to ensure robust fixes and prevent recurrence.
Use cases include failing tests, broken builds, runtime bugs, and production incidents across software projects.

Quick Start

Reproduce the failure locally, then follow the triage checklist to identify the root cause and implement a verified 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 systematically debug a runtime bug or production incident?▼

Systematic debugging requires a stepwise triage checklist to reproduce the failure locally, isolate faulty components, trace failure origins, and implement a verified fix. This process ensures robust remediation and prevents recurrence.

What is the Stop-the-Line rule for incident response and triage?▼

The Stop-the-Line rule halts all feature work immediately to diagnose failures and stabilize systems. This incident response strategy preserves evidence and reduces mean time to recovery (MTTR) without guessing.

How do I find the root cause of failing tests and broken builds?▼

To find the root cause of failing tests, you must reproduce the issue locally and isolate faulty components. Following a structured process of reduction and localization traces the failure origin to enable a verified fix.

What is the best way to reproduce and localize a software failure?▼

The best way to reproduce and localize a software failure is to reproduce the issue locally, then reduce it to a minimal reproduction. This isolates the faulty components and traces the exact failure origin for root-cause verification.

Can I use this debugging process for test failures and build breaks across software projects?▼

Yes, this structured debugging process applies to test failures, broken builds, runtime bugs, and production incidents across software projects. It provides guided remediation through reproduce, localize, reduce, fix, and verify steps.

Why do I need regression testing after implementing a bug fix?▼

Regression testing is required after a bug fix to verify the root cause is resolved and prevent recurrence. End-to-end validation ensures the remediation satisfies functional guidelines without introducing new failures.