debugging-and-error-recovery

Diagnose and fix root causes of test failures, build breaks, and runtime bugs.

1|1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Borisserz/FoodTracker --skill debugging-and-error-recovery-borisserz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/Borisserz/FoodTracker/tree/main/.agents/skills/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/Borisserz/FoodTracker --skill debugging-and-error-recovery-borisserz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides engineers through a disciplined, repeatable approach to identify, diagnose, and remedy root causes when tests fail, builds break, or runtime behavior diverges from expectations.

Core Features & Use Cases

  • Structured triage with preservation of evidence to prevent scope creep
  • Step-by-step localization, reproduction, and diagnosis across UI, API, database, and tooling layers
  • Guidance to implement durable fixes and guard against regressions with verification and postmortems

Quick Start

Start by preserving evidence, reproduce the failure, perform structured triage, diagnose the root cause, implement a fix, and verify the outcome.

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 build break or test failure?

Perform structured triage by preserving evidence, reproducing the failure, diagnosing the root cause, implementing a fix, and verifying the outcome to ensure durable resolution of build breaks and test failures.

What is structured triage and when do I need it for incident management?

Structured triage is a disciplined approach to incident management that preserves evidence and prevents scope creep. You need it when diagnosing runtime bugs, test failures, or build breaks to ensure accurate localization and reproducibility across UI, API, and database layers.

How do I reproduce a runtime bug across different software layers?

Reproduce a runtime bug by following step-by-step localization procedures across UI, API, database, and tooling layers to preserve evidence and accurately diagnose the root cause before implementing a fix.

Can I use this structured debugging approach for production incidents and CI/CD pipeline failures?

Yes, this debugging approach applies to incident reports and failures across development, CI/CD, and production environments, guiding engineers through evidence preservation, root cause diagnosis, and verification to prevent regressions.

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

Prevent regressions after fixing a software bug by enforcing verification steps and conducting postmortems, ensuring the fix is durable and guards against future failures across the software project.