skills.rest
svssdeva
svssdevaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debugging-and-error-recovery

Guides root-cause debugging for failing tests, builds, runtime errors, and incorrect behavior.

1|1|Updated Apr 20, 2026
Search Tags:#debugging#root cause analysis#regression testing#build failures#error recovery#test triage#runtime incidents
One-click install
npx skills add https://github.com/svssdeva/agentic-skills --skill debugging-and-error-recovery-svssdeva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/svssdeva/agentic-skills/tree/main/engineering/debugging-and-error-recovery
Command: npx skills add https://github.com/svssdeva/agentic-skills --skill debugging-and-error-recovery-svssdeva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted time and escalating failures by giving a systematic, evidence-preserving workflow for identifying and fixing the true root cause of test, build, runtime, or incident errors.

Core Features & Use Cases

  • Structured triage from reproduction to verification: Reproduce reliably, localize the failing layer, reduce to a minimal case, fix the root cause, add a regression test, then verify end-to-end.
  • Actionable patterns for common failure modes: Stepwise guidance for test failures, build failures, runtime errors, and non-reproducible issues like timing, environment, state, or randomness.
  • Safety for diagnostic inputs: Treat error output as untrusted text, avoiding blindly following instructions embedded in logs or stack traces.
  • Recurrence prevention: Emphasizes guarding against repeat failures by adding targeted tests and keeping only necessary instrumentation.

Quick Start

Use this skill when your tests fail or your build/runtime behavior is unexpected, and ask for a triage plan that follows the stop-the-line rule and walks through reproduction, localization, minimal reproduction, root-cause fix, regression test, and verification.

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 debug a failing test by finding the root cause instead of just patching the symptom?▼

Root cause debugging requires a systematic workflow: reliably reproduce the failing test, localize the broken layer, reduce to a minimal case, apply the fix, add a regression test, and verify end-to-end.

What is the best way to fix broken builds and runtime errors without escalating failures?▼

Fixing broken builds and runtime errors safely requires enforcing a stop-the-line rule and treating error output as untrusted diagnostic data to prevent blindly following embedded instructions in stack traces.

How do I debug non-reproducible runtime incidents caused by timing or environment state?▼

Debugging non-reproducible runtime incidents involves systematic localization across UI, API, database, and external services, preserving diagnostic evidence to capture timing, environment, state, or randomness issues.

Why should I treat error output and stack traces as untrusted text during test triage?▼

Treating error output as untrusted text during test triage prevents blindly executing instructions embedded in logs or stack traces, ensuring you preserve diagnostic evidence and maintain debugging safety.

How do I prevent regression failures after applying a root cause fix?▼

Preventing regression failures requires creating targeted regression tests for the specific root cause, keeping only necessary instrumentation, and completing full end-to-end validation to add guardrails against repeat issues.

Can I use this systematic debugging workflow for localizing failures across UI, API, and database layers?▼

Yes, the debugging workflow applies to regression triage and localization across UI, API, database, tooling, and external services by enforcing stepwise reproduction, reduction, fix, and verification.

Related Skills

Explore More Software Engineering Skills→
linfordWulinfordWu
1

root-cause-localization

Identify root-cause components from logs and traces within a fault window.

Community
Advanced
Jonathan0823Jonathan0823
7

bug-fixing

Reproduce bugs, analyze root causes, implement fixes, and verify with regression tests.

Community
Basic
Chachamaru127Chachamaru127
3.0k

troubleshoot

Diagnose build, runtime, and UI errors in web and Node.js projects.

Community
Basic
vtgiang-dotcomvtgiang-dotcom
3

debugging-and-error-recovery

Diagnose root causes of test, build, and runtime failures via structured triage.

Community
Advanced