debugging-and-error-recovery

Guide root-cause debugging for failing tests, broken builds, and runtime errors.

9|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/klh/speedy-claude --skill debugging-and-error-recovery-klh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/klh/speedy-claude/tree/main/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/klh/speedy-claude --skill debugging-and-error-recovery-klh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When tests fail, builds break, or runtime behavior diverges from expectations, teams often guess fixes, skip reproduction, or patch symptoms leading to regressions and wasted time. This Skill provides a structured triage process to preserve evidence, reproduce failures, and reach the true root cause so fixes are reliable and verifiable.

Core Features & Use Cases

  • Reproducibility first: Emphasizes reproducing failures reliably before making changes.
  • Localization and reduction: Guides narrowing the failing layer and creating minimal repro cases to clarify causes.
  • Fix, guard, verify: Instructs how to fix the root cause, add regression tests, and verify end-to-end to prevent recurrence.
  • Use case: A CI test suite begins failing after a dependency bump; follow the triage checklist to reproduce in a clean environment, bisect commits if needed, produce a minimal failing test, apply a fix, and add a regression test so CI remains green.

Quick Start

Run the failing test locally, create a minimal reproducible case, identify and fix the root cause, add a regression test, and verify the full test suite and build succeed.

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 failing tests and find the root cause?

To debug flaky or non-reproducible bugs, you must first preserve evidence and establish reproducibility by creating a minimal failing test case, which clarifies the exact conditions triggering the unexpected behavior before applying any fix.

How do I fix CI test regressions after a dependency bump?

To fix CI test regressions after a dependency bump, reproduce the failure locally, use bisect guidance to isolate the breaking commit, apply a root-cause fix, and add a regression test to verify the full test suite remains green.

How do I handle production incident response and runtime errors?

Production incident response for runtime errors requires structured triage to preserve evidence, reproduce the unexpected behavior safely, and apply a reliable fix while following safety rules that avoid executing untrusted commands from error output.

Can I use this triage process for non-reproducible bugs in local development?

Yes, you can use this triage process for non-reproducible bugs in local development by applying localization and reduction techniques to narrow the failing layer and create a minimal repro case that clarifies the underlying cause.

What are the limitations of guessing fixes for broken builds without reproducing failures?

Guessing fixes for broken builds without reproducing failures often leads to patching symptoms and skipping root cause analysis, which causes recurring regressions and wasted time instead of providing reliable and verifiable end-to-end recovery.