skills.rest
vtgiang-dotcom
vtgiang-dotcomCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debugging-and-recovery

Diagnose and resolve software failures through a structured triage process.

3|Updated Apr 1, 2026
Search Tags:#debugging#triage#root-cause#reproduction#incident-response#regression-testing#qa-process
One-click install
npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill debugging-and-recovery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-recovery
Source: https://github.com/vtgiang-dotcom/Solo-Code-Harness/tree/main/.github/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill debugging-and-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a structured approach to triage, reproduce, localize, and fix root causes, reducing guesswork and preventing regression.

Core Features & Use Cases

  • Triage-driven: Immediate stop-the-line rule, evidence preservation, and structured diagnosis.
  • Stepwise debugging: Reproduce, localize, reduce to minimal failing case, and verify end-to-end fixes.
  • Guardrails and tests: Add regression tests to prevent recurrence and verify resolution.

Quick Start

Apply the triage checklist to a failing test or build, starting by reproducing the failure and preserving evidence.

Frequently Asked Questions about debugging-and-recovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is systematic debugging and triage for software failures?▼

Systematic debugging is a structured triage process that diagnoses software failures by enforcing a stop-the-line rule, preserving evidence, and systematically reproducing and localizing the issue to find the root cause.

How do I reproduce and localize a runtime bug or production incident?▼

To reproduce and localize a runtime bug, apply a structured cycle: reproduce the failure locally, reduce it to a minimal failing case, apply the fix, and then verify the resolution end-to-end across UI, API, or data layers.

Does this debugging approach work for both build breaks and production incidents?▼

Yes, this triage-driven debugging approach applies to test failures, build breaks, runtime bugs, and production incidents, systematically diagnosing issues across UI, API, and data layers to isolate root causes.

What is the best way to prevent regression after fixing a software bug?▼

The best way to prevent regression is to add regression tests immediately after applying a fix, ensuring the resolution is verified end-to-end and guarding against the recurrence of the same failure.

Why does my QA process fail to catch recurring software bugs?▼

A QA process may fail to catch recurring bugs if it lacks structured root-cause analysis and regression testing, allowing underlying issues to persist without being reduced to minimal failing cases and properly resolved.

Related Skills

Explore More Software Engineering Skills→
HellKaiser45HellKaiser45

debugging-and-error-recovery

Guide systematic root-cause debugging through reproduce, localize, reduce, fix, and verify steps.

Community
Advanced
TestAny-ioTestAny-io
79

debug

Diagnose Testany test failures by analyzing execution logs and identifying root causes.

Official
Intermediate
hpsgdhpsgd

write-bug-report

Generate structured bug reports from raw descriptions with mandatory sections.

Official
Advanced
yolo-labs-hqyolo-labs-hq

debugging-and-error-recovery

Diagnose reproducible bugs using a structured six-step triage workflow.

Official
Advanced