skills.rest
alissonpef
alissonpefCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debugging-and-error-recovery

Diagnose root causes of failing tests, broken builds, and runtime bugs.

Updated Apr 21, 2026
Search Tags:#testing#debugging#root cause#bug fixing#build failures#error recovery
One-click install
npx skills add https://github.com/alissonpef/copilot-agent-skills --skill debugging-and-error-recovery-alissonpef
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/alissonpef/copilot-agent-skills/tree/main/.github/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/alissonpef/copilot-agent-skills --skill debugging-and-error-recovery-alissonpef

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you diagnose failures systematically when tests break, builds fail, runtime behavior changes, or unexpected errors appear. It prevents guesswork by guiding you to reproduce the issue, localize the failure, fix the underlying cause, and verify that it does not return.

Core Features & Use Cases

  • Structured Triage: Reproduce, localize, reduce, fix, guard, and verify in a disciplined order.
  • Root-Cause Focus: Separates symptom fixes from the actual underlying defect so you avoid temporary patches.
  • Regression Protection: Encourages adding tests and end-to-end verification after a bug fix.
  • Use Cases: Debugging failing test suites, broken builds, flaky runtime bugs, integration issues, and production incidents with clear evidence and safe fallback patterns.

Quick Start

Use this skill to investigate the failing test, reproduce the error, and trace it to the root cause before making any fix.

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 find the root cause of failing tests and broken builds?▼

To find the root cause of failing tests and broken builds, apply a structured reproduce-localize-reduce-fix-guard-verify workflow to systematically isolate the underlying defect rather than applying temporary patches.

What is the best way to debug flaky tests and runtime bugs?▼

The best way to debug flaky tests and runtime bugs is to separate symptom fixes from the actual defect, preserve safe evidence, and add regression tests to verify the error does not return.

How do I fix production incidents without causing regression issues?▼

Fix production incidents without causing regression issues by preserving safe fallback patterns, resolving the underlying cause, and creating end-to-end verification tests to guard against future recurrence.

Does this structured debugging workflow apply to frontend, backend, and database errors?▼

Yes, this structured debugging workflow applies to frontend, backend, database, and build tooling errors, guiding you to reproduce the error and trace it to the root cause before making any fix.

Why should I use a structured triage process for bug fixing instead of patching symptoms?▼

You should use a structured triage process for bug fixing because it separates symptom fixes from the actual underlying defect, ensuring you avoid temporary patches and prevent the unexpected error from returning.

Related Skills

Explore More Software Engineering Skills→
vadimcomanescuvadimcomanescu
24

error-resolver

Diagnose software and runtime errors to identify root causes.

Community
Advanced
TestAny-ioTestAny-io
79

debug

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

Official
Intermediate
troykellytroykelly
11

ci-monitoring

Monitor CI pipelines, diagnose failures, and document fixes until green.

Community
Advanced
ppiankovppiankov

logtap

Captures, triages, and analyzes ephemeral Kubernetes logs in real-time via CLI and sidecar injection.

Community
Advanced