debugging-and-error-recovery

Name: debugging-and-error-recovery
Availability: InStock
Author: cookeyholder

Guide debugging triage from reproduction to root cause verification.

Updated Apr 9, 2026

Search Tags:#debugging #checklist #reproduce #triage #root-cause #incident-management

Ready to run

npx skills add https://github.com/cookeyholder/django-devcontainer-template --skill debugging-and-error-recovery-cookeyholder

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with structured triage. When something breaks, stop adding features, preserve evidence, and follow a structured process to find and fix the root cause. Guessing wastes time. The triage checklist works for test failures, build errors, runtime bugs, and production incidents.

Core Features & Use Cases

The Stop-the-Line Rule: halt feature work when something unexpected happens and preserve evidence (logs, error outputs, repro steps) to prevent compounding issues.
The Triage Checklist: a stepwise approach to reproduction, localization, reduction, root-cause repair, recurrence guards, and end-to-end verification.
Incident-ready workflow: guidance that applies to tests, builds, runtime behavior, and production incidents, ensuring deterministic triage and reliable fixes.

Quick Start

Describe a failing scenario, reproduce it locally, and apply the triage steps to locate 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

How do I systematically debug a runtime bug instead of guessing?▼

Systematic debugging uses a structured triage checklist to find the root cause. It guides you through a six-step reproduce, localize, reduce, fix, guard, and verify workflow instead of guessing.

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

The stop-the-line rule in incident management halts feature work when an unexpected failure occurs. It preserves evidence like logs and reproduction steps to prevent compounding issues during root-cause triage.

How do I triage test failures and build errors step by step?▼

Triage test failures and build errors using a stepwise approach. You reproduce the error, localize the failing component, reduce the test case, repair the root cause, add guards, and verify the fix end-to-end.

Can I use this debugging checklist for production incidents?▼

Yes, you can use this debugging checklist for production incidents. It provides an incident-ready workflow that applies deterministic triage steps to preserve evidence and ensure reliable root-cause fixes.

What is the best way to reproduce and localize a runtime bug?▼

The best way to reproduce and localize a runtime bug is to describe the failing scenario, reproduce it locally, and apply triage steps. This structured reduction isolates the exact root cause for repair.