skills.rest
cyalcala
cyalcalaCOMMUNITY
Explore all skills by this author →
GitHub

debugging-and-error-recovery

Diagnose root causes in failing tests, builds, and runtime errors via structured triage.

1|Updated Mar 17, 2026
Search Tags:#debugging#triage#root-cause#reproduction#incident-management#test-failure
One-click install
npx skills add https://github.com/cyalcala/va-freelance-hub --skill debugging-and-error-recovery-cyalcala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/cyalcala/va-freelance-hub/tree/main/.antigravity/skills_old_tainted/debugging-and-error-recovery
Command: npx skills add https://github.com/cyalcala/va-freelance-hub --skill debugging-and-error-recovery-cyalcala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with structured triage to stop guessing and quickly identify the root cause of failures across tests, builds, and production incidents.

Core Features & Use Cases

  • Stop-the-Line rule to prevent scope creep and preserve evidence during incidents.
  • Triage steps: Reproduce, Localize, Reduce, Fix, Guard against recurrence, and Verify End-to-End.
  • Guidance for failures across UI, API, and CI pipelines, including reproducible repros and robust verification.

Quick Start

Begin by reproducing the failure and then proceed through localization, creating a minimal repro, applying a root-cause fix, adding a regression guard, and verifying end-to-end.

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 systematically debug a failing test instead of guessing the root cause?▼

Systematic debugging requires structured triage steps: reproduce the failure, localize the issue, reduce to a minimal repro, apply a root-cause fix, add a regression guard, and verify end-to-end.

What is the best way to triage runtime errors across UI, API, and CI pipelines?▼

Triage runtime errors by applying a stop-the-line rule to preserve evidence, then systematically reproduce, localize, and reduce the error across UI, API, and CI environments before fixing.

How do I create a minimal reproduction case for a build failure?▼

Create a minimal reproduction for build failures by reducing the failing scenario to its simplest form during the localization step, ensuring the core issue is isolated before applying a fix.

How do I prevent regression after fixing a production incident?▼

Prevent regression after fixing a production incident by adding a regression guard during the fix phase, then verifying the solution end-to-end to ensure the original failure does not recur.

Does this debugging workflow require specific dependencies or tools to operate?▼

No dependencies are required. The debugging workflow operates as a structured methodology applicable across any software development environment without needing specific external tools or components.

Why should I use a structured triage process for test failures instead of ad-hoc debugging?▼

Structured triage stops guesswork by enforcing a stop-the-line rule to preserve evidence and scope, ensuring root causes are quickly identified through reproducible cases rather than trial and error.

Related Skills

Explore More Software Engineering Skills→
abnegateabnegate
2

debug

Reproduce and fix failing Gradle tests and build errors in Java/Kotlin projects.

Community
Advanced
fmflurryfmflurry
171

eslint-true-server-error-resolution-2

Identify and resolve recurring software errors with a repeatable resolution pattern.

Community
Intermediate
zerAdazerAda

bmad-qa-generate-e2e-tests

Generate end-to-end API and UI tests for identified application features.

Community
Advanced
arvindbattulaarvindbattula

debugging

Diagnose root-cause failures with a structured triage workflow.

Community
Advanced