skills.rest
akbarhlubis
akbarhlubisCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debugging-and-error-recovery

Diagnose software issues through root-cause analysis and systematic debugging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a structured approach to debugging and error recovery, helping users identify and fix the root cause of issues efficiently.

Core Features & Use Cases

  • Systematic Debugging: Offers a step-by-step process to systematically diagnose and resolve issues.
  • Triage Checklist: Provides a comprehensive checklist for reproducibility, localization, reduction, and root cause analysis.
  • Error-Specific Patterns: Includes strategies for handling common errors like test failures, build issues, and runtime errors.
  • Safe Fallback Patterns: Suggests safe fallbacks for when under time pressure, such as using default configurations or graceful degradation.
  • Instrumentation Guidelines: Offers guidelines on when and how to add and remove logging for effective debugging.

Quick Start

Use the debugging-and-error-recovery skill to diagnose and fix a runtime error in your codebase.

Frequently Asked Questions about debugging-and-error-recovery

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

FAQPage Schema
What is systematic root cause analysis in software debugging?▼

Systematic root cause analysis is a structured debugging approach focusing on reproducibility, localization, and reduction to identify the exact origin of software errors rather than just treating symptoms.

How do I debug a runtime error systematically?▼

To debug a runtime error systematically, follow a triage checklist for reproducibility and localization, apply error-specific patterns for runtime bugs, and add instrumentation to isolate the root cause.

What is the best way to fix persistent test failures and build errors?▼

The best way to fix persistent test failures and build errors is using a structured debugging process that reduces the problem scope and applies targeted error-specific resolution patterns.

When should I add or remove logging for effective debugging?▼

You should add logging during debugging to improve instrumentation and trace execution flow, and remove it once root cause analysis is complete to maintain clean production code.

What safe fallback patterns can I use when debugging under time pressure?▼

When debugging under time pressure, safe fallback patterns include using default configurations or implementing graceful degradation to maintain system stability while deferring full root cause resolution.

Related Skills

Explore More Software Engineering Skills→
GrishaAngelovGHGrishaAngelovGH
15

bug-investigator

Reproduce software defects and generate failing tests for root-cause analysis.

Community
Advanced
smarmen86smarmen86

ios-fix

Identify, patch, and verify iOS application bugs within a CI loop.

Community
Advanced
CJ-1981CJ-1981

moai-workflow-testing

Manage Python software development lifecycle with pytest, pylint, bandit, and mypy.

Community
Advanced
geoffjaygeoffjay
8

tokio-troubleshooting

Diagnose deadlocks, leaks, and performance issues in Tokio runtimes.

Community
Advanced