addy-debugging-and-error-recovery

Triage software failures with a stepwise workflow to identify root causes.

Updated Mar 19, 2026

Search Tags:#debugging #quality #recovery #triage #reproducibility #root-cause #incident-management

Ready to run

npx skills add https://github.com/japurcell/skills --skill addy-debugging-and-error-recovery

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides engineers through a structured, repeatable debugging process to identify and fix root causes instead of patching symptoms.

Core Features & Use Cases

Structured triage: Follow a step-by-step checklist from reproduction to verification to isolate the failure.
Stop-the-Line discipline: Enforce a rule to pause feature work when incidents occur, preserving evidence and preventing escalation.
Guardrails and documentation: Capture evidence, decisions, and verification steps to prevent recurrence and improve learning.

Quick Start

Apply the Step 1-6 triage workflow to reproduce the failure, localize the cause, reduce the case to its minimal form, implement a root-cause fix, and verify end-to-end before resuming work.

Frequently Asked Questions about addy-debugging-and-error-recovery

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

FAQPage Schema

How do I systematically debug software failures to find the root cause?▼

Systematic debugging triages software failures through a stepwise workflow from reproduction to verification, isolating the root cause rather than patching symptoms. It applies to test failures, build errors, runtime bugs, and production incidents.

What is the stop-the-line rule in incident management debugging?▼

The stop-the-line rule in incident management pauses feature work when incidents occur, preserving evidence and preventing escalation. This discipline maintains a structured environment to accurately diagnose software failures.

How do I create guardrails to prevent software bug recurrence after a fix?▼

Creating guardrails to prevent bug recurrence involves capturing evidence, decisions, and verification steps during the debugging process. This documentation prevents future failures and improves team learning after resolving runtime bugs or build errors.

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

The best way to triage a production incident is following a structured checklist that reproduces the failure, localizes the cause, reduces the case to its minimal form, and verifies the root-cause fix end-to-end before resuming work.

Does structured root-cause analysis work for both test failures and build errors?▼

Structured root-cause analysis works effectively for test failures, build errors, runtime bugs, and production incidents. It applies a repeatable step-by-step triage workflow to isolate the failure and implement a verified fix.

When should I enforce the stop-the-line rule during runtime bug recovery?▼

You should enforce the stop-the-line rule immediately when runtime bugs or production incidents occur. This pause preserves critical debugging evidence, prevents further escalation, and ensures a systematic root-cause diagnosis.