skills.rest
udsy19
udsy19COMMUNITY
Explore all skills by this author →
GitHub

debugging-and-error-recovery

Guide structured debugging to identify and resolve code errors.

Updated Jun 24, 2026
Search Tags:#code analysis#debugging#systematic approach#root cause analysis#error recovery
One-click install
npx skills add https://github.com/udsy19/.claude --skill debugging-and-error-recovery-udsy19
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-and-error-recovery
Source: https://github.com/udsy19/.claude/tree/main/skills/debugging-and-error-recovery
Command: npx skills add https://github.com/udsy19/.claude --skill debugging-and-error-recovery-udsy19

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured process for debugging and error recovery, helping users systematically identify and fix the root cause of issues in their code or applications.

Core Features & Use Cases

  • Systematic Debugging: Offers a checklist-based approach to diagnose and resolve errors efficiently.
  • Stop-the-Line Rule: Encourages halting development and preserving evidence when errors occur.
  • Triage Checklist: Guides users through reproducing errors, narrowing down the issue, reducing the problem to a minimal case, and fixing the root cause.
  • Error-Specific Patterns: Provides specific strategies for dealing with common error scenarios like test failures, build errors, and runtime bugs.
  • Safe Fallback Patterns: Offers code examples for graceful degradation and error handling.
  • Instrumentation Guidelines: Provides best practices for adding and removing logging in code.
  • Common Rationalizations: Debunks common misconceptions in debugging.
  • Treating Error Output as Untrusted Data: Emphasizes the importance of verifying error messages and outputs.
  • Red Flags: Identifies signs of problematic debugging practices.
  • Verification: Outlines steps to ensure a bug is truly fixed.

Quick Start

Execute the debugging skill to start the systematic process of diagnosing the error.

Frequently Asked Questions about debugging-and-error-recovery

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

FAQPage Schema
What is a systematic approach to debugging and error recovery?▼

A systematic approach to debugging uses a triage checklist to reproduce errors, narrow down causes, reduce to minimal cases, and fix root causes. It emphasizes preserving evidence and halting development when errors occur.

How do I find the root cause of a runtime bug or build error?▼

To find the root cause of a runtime bug or build error, follow error-specific patterns to reproduce the issue, narrow down the scope, and reduce it to a minimal case before implementing a targeted fix.

What are the best practices for adding logging and instrumentation during code analysis?▼

Best practices for instrumentation involve adding and removing logging systematically during code analysis to capture runtime behavior, while treating error output as untrusted data that requires verification.

How do I verify that a bug is truly fixed after implementing error recovery?▼

To verify a bug is truly fixed after error recovery, follow structured verification steps that confirm the original issue is resolved and ensure safe fallback patterns like graceful degradation are properly implemented.

Why should I treat error messages as untrusted data during root cause analysis?▼

Treating error messages as untrusted data during root cause analysis prevents misleading diagnoses, ensuring you verify outputs rather than relying on common rationalizations or assumptions about the failure.

What are common red flags and misconceptions to avoid when debugging code?▼

Common red flags in debugging code include relying on rationalizations instead of evidence and ignoring systematic triage. Avoid these problematic practices by strictly following a structured debugging process.

Related Skills

Explore More Software Engineering Skills→
ssimhanssimhan
1

debugging

Reproduce software defects and verify fixes with evidence-based workflows.

Community
Basic
etretr
41

debugging

Identify and prove bug root causes through a structured five-phase workflow.

Community
Advanced
dmitriiwebdmitriiweb
109

debug-logging-assistant

Add debug logging statements to code without altering program behavior.

Community
Intermediate
zach-sourcezach-source

replay-buffer

Look up known fixes for tool, test, and build failures.

Community
Advanced