audit-errors

Audit code for error-handling anti-patterns and silent failures.

1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/SebKay/skills --skill audit-errors
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-errors
Source: https://github.com/SebKay/skills/tree/main/audit-errors
Command: npx skills add https://github.com/SebKay/skills --skill audit-errors

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify and fix inconsistencies, anti-patterns, and silent failures in error handling within code, ensuring that errors are managed reliably and don't get lost or masked.

Core Features & Use Cases

  • Error Path Auditing: Maps and analyzes failure boundaries across various code components.
  • Risk Pattern Detection: Searches for common risky patterns like swallowed errors, misleading fallbacks, and inconsistent translation.
  • Anti-Pattern Identification: Detects specific anti-patterns such as overbroad catches, lost context, and async blind spots.
  • Prioritization: Classifies findings into severity levels (P1-P4).
  • Auto-fixing: Safely auto-fixes local, low-risk issues.
  • Use Case: When reviewing a complex asynchronous workflow, use this Skill to ensure that all potential error paths are identified, consistently handled, and that no errors are silently dropped.

Quick Start

Audit the error handling in the provided controller code for silent failures and inconsistent translation.

Frequently Asked Questions about audit-errors

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

FAQPage Schema
How do I audit code for empty catch blocks and silent error failures?

To audit code for silent failures, you map failure boundaries and detect anti-patterns like empty catch blocks, swallowed promise rejections, and log-and-continue paths to ensure errors are managed reliably without being masked.

What is the best way to find ignored promise rejections in asynchronous workflows?

Finding ignored promise rejections involves analyzing asynchronous workflows to identify async blind spots and overbroad catches. By mapping these error paths, you can ensure consistent error translation and prevent dropped failures.

How do I prioritize error handling anti-patterns found during a code review?

You prioritize error handling anti-patterns by classifying findings into severity levels ranging from P1 to P4. This allows you to address critical silent failures and inconsistent error translation before moving on to lower-risk issues.

Can I automatically fix inconsistent error handling and misleading fallback values?

Yes, you can automatically fix local, low-risk error handling issues like misleading fallback values. The auditing process safely applies auto-fixes to these specific anti-patterns while leaving complex failures for manual review.

Does this error path auditing approach work for complex asynchronous workflows?

Yes, error path auditing works for complex asynchronous workflows by specifically analyzing async blind spots and failure boundaries. It ensures all potential error paths are identified and consistently handled without dropping errors.

What are common error handling anti-patterns that hide faults in software?

Common error handling anti-patterns that hide faults include swallowed errors, log-and-continue paths, misleading fallback values, overbroad catches, and inconsistent error translation across application layers.