skills.rest
d0whc3r
d0whc3rCOMMUNITY
Explore all skills by this author →
GitHub

debugging-and-error-recovery

Guide systematic triage to reproduce, localize, and fix failing tests and builds.

2|Updated Feb 16, 2026
Search Tags:#debugging#root cause analysis#incident response#regression testing#build failures#error recovery#runtime triage
One-click install
npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill debugging-and-error-recovery-d0whc3r
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/d0whc3r/statsig-browser-extension/tree/main/.agents/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill debugging-and-error-recovery-d0whc3r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you stop compounding failures by guiding you through systematic triage to reproduce, localize, and fix the underlying root cause of tests, builds, and runtime errors.

Core Features & Use Cases

  • Structured triage workflow: Follow an ordered checklist (reproduce → localize → reduce → fix → guard → verify) to prevent symptom-chasing.
  • Regression-proofing: Convert the discovered issue into a targeted guardrail test so the failure is caught next time.
  • Practical error-specific patterns: Use common decision trees for test failures, build failures, and runtime exceptions (including flaky or non-reproducible cases).

Quick Start

Use this debugging-and-error-recovery skill when a test fails or a runtime error appears and you need a reliable, step-by-step plan to reproduce, isolate, and fix the true cause.

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 broken builds without guessing?▼

Systematic root cause analysis requires an ordered checklist: reproduce the failure, localize the issue, minimize the test case, fix the root cause, add a regression test, and verify the end-to-end behavior to prevent compounding failures.

How do I find the root cause of non-reproducible and flaky runtime exceptions?▼

Triage non-reproducible issues across UI, API, database, tooling, and external services by applying targeted decision trees that isolate environment-dependent failures and transform vague symptoms into reproducible evidence.

Does root cause analysis work for environment-dependent failures across external services?▼

Yes, root cause analysis applies to environment-dependent failures across UI, API, database, tooling, and external services by guiding you through reproducing and localizing the failure within its specific runtime context.

How do I prevent regression bugs after fixing an unexpected runtime error?▼

Prevent regression bugs by converting the discovered issue into a targeted guardrail test during the recovery workflow, ensuring the specific failure is caught automatically if it reappears in future builds.

What are the limitations of symptom-chasing when triaging runtime errors?▼

Symptom-chasing during runtime triage leads to compounding failures because it skips the ordered workflow of reproducing, localizing, and minimizing the issue, meaning the true root cause remains unfixed and triggers future regressions.

Related Skills

Explore More Software Engineering Skills→
klhklh
9

systematic-debugging

Trace software bugs and test failures to their root causes.

Community
Intermediate
ydnikolaevydnikolaev
8

debugger

Debug runtime errors and failing tests with a seven-step workflow.

Community
Basic
mattdurhammattdurham
9

error-detective

Analyze logs, traces, and metrics to diagnose root causes across distributed systems.

Community
Advanced
mortenbroesbymortenbroesby
1

debugging-and-error-recovery

Diagnose software failures and triage issues to shorten recovery time.

Community
Advanced