silent-failure-hunter

Audit error handling code for silent failures and unjustified fallbacks.

4|Updated Mar 13, 2026

Search Tags:#code review #debugging #error handling #logging #fallbacks #silent failures

Ready to run

npx skills add https://github.com/euxx/claude-skills-for-copilot --skill silent-failure-hunter-euxx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: silent-failure-hunter
Source: https://github.com/euxx/claude-skills-for-copilot/tree/main/skills/silent-failure-hunter
Command: npx skills add https://github.com/euxx/claude-skills-for-copilot --skill silent-failure-hunter-euxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you find error handling that hides failures, gives users unclear feedback, or relies on unjustified fallback behavior. It is built for code paths where problems are easy to miss but expensive to debug later.

Core Features & Use Cases

Silent Failure Detection: Flags empty catch blocks, swallowed exceptions, and error handlers that continue without proper reporting.
Fallback Review: Evaluates whether default values, retries, or alternate paths are explicit, justified, and safe.
User Feedback Audit: Checks that failures produce actionable messages instead of vague logs or hidden state changes.
Use Case: Use it after changing API calls, file operations, event handlers, or retry logic to catch errors that would otherwise disappear unnoticed.

Quick Start

Review the selected file or directory with the silent-failure-hunter skill to identify hidden failures, weak error messages, and unjustified fallbacks.

Frequently Asked Questions about silent-failure-hunter

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

FAQPage Schema

How do I catch silent failures in error handling code like empty catch blocks?▼

Catching silent failures requires auditing try/catch blocks, error callbacks, and fallback paths to flag swallowed exceptions and empty handlers. This skill reviews code to ensure hidden failures are logged precisely and receive actionable user messaging instead of disappearing unnoticed.

What is the best way to review fallback logic and default values for hidden errors?▼

Reviewing fallback logic involves evaluating whether default values, retries, and alternate paths are explicit, justified, and safe. This skill audits fallback behavior to identify unjustified defaults that mask failures and ensures error paths propagate issues correctly.

How do I check that my error callbacks and exception handling provide actionable user feedback?▼

Checking error callbacks involves auditing failure paths for actionable user messages instead of vague logs or hidden state changes. This skill verifies that exceptions are handled specifically and that failures produce clear, actionable messaging for users.

Can I use this to audit retry logic and optional chaining for swallowed exceptions?▼

You can audit retry logic and optional chaining used where explicit handling is required. This skill evaluates retry paths and optional chaining syntax to detect swallowed exceptions, inadequate reporting, and unjustified fallback behavior that hides failures.

When should I run an audit for silent failures in my codebase?▼

You should run a silent failure audit after changing API calls, file operations, event handlers, or retry logic. This skill catches errors that would otherwise disappear unnoticed in code paths where problems are easy to miss but expensive to debug later.

Why does my error handling continue without proper reporting after a caught exception?▼

Error handling continues without reporting when catch blocks swallow exceptions or use unjustified fallback behavior. This skill flags empty catch blocks, swallowed exceptions, and error handlers that continue without proper logging or specific exception handling.