skills.rest
1J6K21
1J6K21COMMUNITY
Explore all skills by this author →
GitHub

debugging-and-error-recovery

Diagnose and resolve software failures with a reproducible triage checklist.

Updated Mar 28, 2026
Search Tags:#debugging#error-recovery#triage#root-cause#regression-testing#build-error#test-failure
One-click install
npx skills add https://github.com/1J6K21/build4good --skill debugging-and-error-recovery-1j6k21
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/1J6K21/build4good/tree/main/.gemini/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/1J6K21/build4good --skill debugging-and-error-recovery-1j6k21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable process for diagnosing and fixing software failures, preventing guesswork and reducing time spent on troubleshooting.

Core Features & Use Cases

  • Triage Checklist: Step‑by‑step guide covering reproduction, localization, reduction, fixing, guarding, and verification.
  • Regression Safeguards: Creates targeted tests to ensure the same issue does not reappear.
  • Scope: Ideal for test failures, broken builds, runtime bugs, and production incidents in any development environment.
  • Example: When a CI pipeline reports a failing test, the Skill walks a developer through reproducing the failure, bisecting commits, and adding a failing‑before‑fix test to lock in the fix.

Quick Start

Ask the skill to guide you through debugging a failing test by following the triage checklist.

Frequently Asked Questions about debugging-and-error-recovery

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

FAQPage Schema
What is the best way to debug a failing test in a CI pipeline?▼

Debugging a broken build involves following a triage checklist to reproduce the error, localize the root cause through commit bisection, and generate regression tests to prevent the build error from recurring.

How do I fix a runtime bug without guessing the root cause?▼

To fix a runtime bug without guessing, follow a structured triage process covering reproduction, localization, and reduction to pinpoint the exact failure, then apply a targeted fix and add a regression test to guard against recurrence.

How do I create regression tests for a production incident?▼

Creating regression tests for a production incident involves generating targeted failing tests that reproduce the incident's exact conditions, ensuring the fix passes the test and preventing the same issue from reappearing.

Does this debugging process work for any development environment?▼

Yes, this debugging process works across any development environment, providing a reproducible triage checklist applicable to test failures, build errors, runtime bugs, and production incidents regardless of the specific platform.

What steps should I take to triage a build error?▼

Triage a build error by following the step-by-step checklist: reproduce the failure, localize the root cause, reduce the problem to its minimal form, apply the fix, and add a regression test to verify the resolution.

Related Skills

Explore More Software Engineering Skills→
oolothooloth
24

inspecting-codefresh-failures

Diagnose Codefresh CI failures and generate structured failure reports.

Community
Advanced
DYAI2025DYAI2025

regression-test-generator

Generate Arrange-Act-Assert regression tests for Jest, Vitest, pytest, or Playwright.

Community
Intermediate
withakaywithakay

ito-commit

Create atomic git commits aligned with Ito change tracking.

Community
Intermediate
Vortex4047Vortex4047

debugging-toolkit-smart-debug

Triages error reports into ranked root-cause hypotheses and validation plans.

Community
Advanced