skills.rest
nassimbf
nassimbfCOMMUNITY
Explore all skills by this author →
GitHub

debugging-and-error-recovery

Diagnose software failures with a structured triage workflow across UI, API, build, and runtime layers.

3|Updated Apr 18, 2026
Search Tags:#debugging#error-recovery#triage#incidents#root-cause#test-failures#build-failures
One-click install
npx skills add https://github.com/nassimbf/ftitos-claude-code --skill debugging-and-error-recovery-nassimbf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/nassimbf/ftitos-claude-code/tree/main/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/nassimbf/ftitos-claude-code --skill debugging-and-error-recovery-nassimbf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with a structured triage approach to stop guessing and preserve evidence when tests fail, builds break, or runtime behavior diverges.

Core Features & Use Cases

  • Triage checklist and stop-the-line rule to preserve evidence and prevent escalation.
  • Step-by-step workflow (Reproduce, Localize, Reduce, Fix, Guard, Verify End-to-End) that guides teams through common failure modes.
  • Incident and bug-resolution playbooks that apply to test failures, build issues, runtime bugs, and production incidents.

Quick Start

Run the Step-by-step triage process from reproducing the failure through end-to-end verification.

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 runtime bugs and test failures?▼

To find the root cause of runtime bugs and test failures, apply a structured triage workflow to reproduce, localize, reduce, and fix the exact failure scenario across UI, API, build, and runtime layers.

What is the best way to triage production incidents without losing evidence?▼

The best way to triage production incidents is applying a stop-the-line rule to preserve evidence and prevent escalation, followed by a step-by-step workflow to reproduce and localize the failure.

How do I fix build failures systematically instead of guessing?▼

To fix build failures systematically, follow a structured triage checklist that guides you through reproducing the issue, reducing the scope, applying the fix, and verifying end-to-end success.

Does systematic debugging work for both UI and API layer failures?▼

Yes, systematic debugging works for UI and API layer failures by applying a structured triage workflow across those layers to identify, document, and fix the exact failure scenario.

How do I prevent bug recurrence after applying a runtime fix?▼

To prevent bug recurrence after applying a runtime fix, ensure guardrails and verification steps are in place to validate end-to-end success and stop the failure from happening again.

Related Skills

Explore More Software Engineering Skills→
thechandanbhagatthechandanbhagat
8

debug

Analyze stack traces and logs to identify root causes and suggest fixes.

Community
Advanced
rkumar261rkumar261
1

land-and-deploy

Merge PRs, wait for CI, deploy to production, and verify canary health.

Community
Advanced
AreteDriverAreteDriver
4

cicd-pipeline

Implements CI/CD pipelines using Batcomputer for automated code review and deployment gating.

Community
Advanced
I194I194
9

canary

Monitor deployed apps for console errors, performance regressions, and page failures.

Community
Advanced