audit-error-handling

Audit and fix error-handling defects across APIs, CLIs, and async tasks.

10|5|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/JHostalek/dotclaude --skill audit-error-handling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-error-handling
Source: https://github.com/JHostalek/dotclaude/tree/main/skills/audit-error-handling
Command: npx skills add https://github.com/JHostalek/dotclaude --skill audit-error-handling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finds error-handling defects that produce false success, corrupt state, lost failures, resource leaks, incomplete recovery, or poor operational visibility.

Core Features & Use Cases

  • Failure-path auditing: Trace errors from their origin through propagation, translation, retries, cleanup, persistence, and terminal boundaries.
  • Contract and state verification: Check whether callers receive truthful outcomes, state remains valid, resources are released, and recovery is bounded.
  • Resilience assessment: Review asynchronous work, cancellation, timeouts, retries, partial failures, startup and shutdown, fallbacks, overload, and recovery behavior.
  • Use Case: Apply the Skill to an API, worker, CLI, or service to identify swallowed exceptions, missing awaits, misleading fallbacks, unhandled entry-point failures, and incomplete cleanup, then make only fixes within the established auto-fix boundary.

Quick Start

Use the audit-error-handling skill on the specified path to inspect every applicable failure boundary, report confirmed defects and residual risks, and apply safe fixes with verification.

Frequently Asked Questions about audit-error-handling

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

FAQPage Schema
How do I audit async code for swallowed exceptions and missing awaits?

Auditing async code for swallowed exceptions involves tracing failure paths from origin to terminal boundaries. This Skill identifies missing awaits and swallowed exceptions in asynchronous tasks, verifying cancellation, timeouts, and incomplete cleanup behavior.

Why does my API return false success when an external dependency fails?

False success occurs when error-handling defects suppress failures from external dependencies. This Skill audits failure propagation and contract verification to ensure callers receive truthful outcomes instead of misleading fallbacks or silently lost errors.

What is the best way to find resource leaks caused by incomplete error recovery?

Finding resource leaks from incomplete error recovery requires tracing cleanup paths during failure states. This Skill audits cleanup behavior across APIs, workers, and persistence layers to verify resources are released and state remains valid during failures.

Can I use this error handling audit on CLI tools and startup or shutdown paths?

Yes, error handling audits apply to CLIs, workers, queues, and services. This Skill inspects startup, shutdown, and operational recovery paths, verifying fault coverage, resilience, and observability across all applicable failure boundaries.

How do I fix silent failures in workers and queues without changing public contracts?

Fixing silent failures in workers and queues requires applying safe fixes within an established auto-fix boundary. This Skill reports confirmed defects, applies bounded recovery corrections, and escalates any changes impacting public contracts or recovery policy.

What limitations exist when auditing error handling for retry and overload behavior?

Auditing retry and overload behavior is limited by the auto-fix boundary. This Skill verifies resilience and recovery behavior but escalates changes to recovery policy, ensuring legitimate behavior is preserved without overriding established fault tolerance contracts.