debugging-and-error-recovery

Automate structured debugging and error-recovery workflows for software failures.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Avila-Tek/avila-tek-skill-pack --skill debugging-and-error-recovery-avila-tek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/Avila-Tek/avila-tek-skill-pack/tree/main/skills/dev-debugging-and-error-recovery
Command: npx skills add https://github.com/Avila-Tek/avila-tek-skill-pack --skill debugging-and-error-recovery-avila-tek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging and error recovery for software failures, guiding engineers from failure detection through root-cause diagnosis and verified fixes, reducing blind guessing.

Core Features & Use Cases

  • Structured triage checklist that preserves evidence (logs, repro steps) and standardizes root-cause analysis.
  • Reproducibility and localization guidance across UI/API/Build/Runtime layers, with step-by-step guidance for minimal repros and validated fixes.
  • Use Case: When a test fails after a code change, follow this skill to reproduce, locate the failing component, and verify end-to-end through end-user workflow.

Quick Start

Identify the failure, reproduce it if possible, and execute the triage checklist to locate and fix the root cause.

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 find the root cause of a failing test or build error?

You can debug a production incident by applying a structured triage process that spans reproduction, localization, and root-cause diagnosis. This ensures evidence preservation and step-by-step recovery for runtime failures.

What is the best way to create a minimal reproduction for a software bug?

The best way to create a minimal reproduction involves following step-by-step localization guidance across UI, API, build, and runtime layers. This isolates the exact failure conditions needed to validate end-to-end fixes.

How do I prevent regression errors after applying a bug fix?

To prevent regression errors after a bug fix, apply guarded fixes and execute regression testing with optional instrumentation. This verifies end-to-end through end-user workflows and ensures the root-cause diagnosis is accurate.

Can I use a structured triage process for CI pipeline failures?

Yes, you can apply structured debugging workflows to CI pipeline failures. The triage process automates error recovery across tests and builds, ensuring reproducibility and root-cause localization for development environments.