debugging-and-error-recovery

Diagnose failing tests and broken builds to identify root causes and recovery steps.

1|Updated Jan 28, 2025

Search Tags:#debugging #bisection #triage #root-cause #incident-response #regression-testing #test-failure

Ready to run

npx skills add https://github.com/josuenavarroaguado/josuenavarroaguado.github.io --skill debugging-and-error-recovery-josuenavarroaguado

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When tests fail, builds break, runtime behavior diverges, or errors appear in logs, teams often guess fixes and create more problems; this Skill provides a structured, evidence-first triage process to reliably identify and fix the root cause and prevent regressions.

Core Features & Use Cases

Reproduce reliably: Steps and techniques to reproduce failures deterministically, including isolating environment, adding instrumentation, and detecting timing or state dependencies.
Localize and reduce: Methods for narrowing the failing layer, using bisection, and creating minimal reproducible cases to expose the true cause.
Fix and guard: Guidance to implement root-cause fixes, add regression tests, and verify end-to-end to prevent recurrence.
Use Case: Recover a CI-failing test introduced after a recent deploy by reproducing locally, bisecting commits, producing a minimal repro, fixing the underlying bug, and adding a test to stop future regressions.

Quick Start

Help me diagnose a failing test by reproducing the failure, isolating and reducing it to a minimal case, recommending a root-cause fix, and proposing a regression test and verification steps.

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 find the root cause of a failing test in CI?▼

To find the root cause of a failing test, reproduce the failure locally, isolate the failing layer, bisect recent commits to locate the regression, and create a minimal reproducible case to expose the underlying bug.

What is the best way to fix flaky tests and prevent regressions?▼

Fix flaky tests by detecting timing or state dependencies during reproduction, implementing a root-cause fix, and adding regression tests with an end-to-end verification plan to prevent future recurrence.

How do I debug build errors and runtime bugs across backend and frontend integrations?▼

Debug build errors and runtime bugs across integrations by applying an evidence-first triage process that narrows the failing layer and uses local instrumentation to identify the exact recovery steps.

What do I need to diagnose production incidents and CI regressions?▼

Diagnosing production incidents and CI regressions requires reproducible steps, access to environment details and logs, and the ability to run local tests and bisect commits to output a verified root-cause fix.

Why does bisection help with triaging test failures and broken builds?▼

Bisection helps triage test failures and broken builds by systematically narrowing down recent commits, reducing the search space to quickly isolate the exact code change that introduced the regression or runtime bug.