skills.rest
LazyIsEfficient
LazyIsEfficientOFFICIAL
Explore all skills by this author →
GitHub

debugging-and-error-recovery

Diagnoses failures through structured reproduction, localization, and root-cause verification.

15|3|Updated Apr 9, 2026
Search Tags:#testing#debugging#verification#triage#reproduction#root-cause-analysis#incident-response
One-click install
npx skills add https://github.com/LazyIsEfficient/agentic-os --skill debugging-and-error-recovery-lazyisefficient
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/LazyIsEfficient/agentic-os/tree/main/.claude/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/LazyIsEfficient/agentic-os --skill debugging-and-error-recovery-lazyisefficient

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematic debugging with structured triage to preserve evidence, reproduce failures reliably, and locate the root cause before applying fixes.

Core Features & Use Cases

  • Stop the line: halt feature work when something unexpected happens to prevent scope creep and additional damage.
  • Preserve evidence: capture error outputs, logs, and steps to reproduce to enable reliable diagnosis.
  • Reproduce before fixing: ensure failures are reproducible before making changes to the code or configuration.
  • Root-cause focus: iterate questions "why" until the actual cause is found, avoiding symptom fixes.
  • Verification and guardrails: include regression tests and end-to-end verification to ensure long-term reliability.

Quick Start

Follow the triage checklist: reproduce the failure, localize the failure layer, reduce to a minimal case, fix the root cause, guard against recurrence, and verify end-to-end.

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 debug runtime bugs and production incidents?▼

Systematic debugging provides a structured triage workflow to diagnose runtime bugs and production incidents. It enforces evidence preservation, reliable reproduction, and root-cause localization before applying any code fixes.

How do I reproduce a test failure reliably before fixing the code?▼

To reproduce a test failure reliably, you must first preserve evidence like error outputs and logs. This structured triage process ensures the failure is consistently reproducible before you attempt code changes.

How do I find the root cause of a build failure instead of just fixing the symptom?▼

Root-cause analysis for a build failure involves iterating 'why' questions until the actual cause is found. This minimizes the failure to a minimal case, avoiding superficial symptom fixes.

When should I stop feature work to triage an unexpected production incident?▼

You should stop feature work immediately during an unexpected production incident to prevent scope creep and additional damage. This 'stop the line' approach captures evidence and halts further system impact.

How do I verify a root-cause fix and prevent bug recurrence?▼

Verify a root-cause fix by implementing regression tests and end-to-end verification. These guardrails ensure long-term reliability and prevent the same failure from recurring in the future.

Related Skills

Explore More Software Engineering Skills→
KILWA73KILWA73

log-aggregator

Extract root-cause insights from noisy error logs and stack traces.

Community
Intermediate
jdeweedatajdeweedata

Bug Fixing Assistant

Diagnose and fix bugs in the CircleTel codebase using a five-phase debugging workflow.

Community
Advanced
codeApe-7codeApe-7
17

sre-engineer

Centralize SRE practices for SLOs, monitoring, and incident response automation.

Community
Advanced
hadimiftahulfhadimiftahulf

debug-protocol

Guide systematic reproduction, root cause analysis, and verification of software bugs.

Community
Intermediate