silent-failure-hunter

Audit codebases for silent failures across error handling, logging, and fallbacks.

1|Updated Feb 25, 2026

Search Tags:#debugging #logging #auditing #reliability #error-handling #code-review

Ready to run

npx skills add https://github.com/bcmcpher/my-skills --skill silent-failure-hunter-bcmcpher

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: silent-failure-hunter
Source: https://github.com/bcmcpher/my-skills/tree/main/plugins/programming-tools/agents/silent-failure-hunter
Command: npx skills add https://github.com/bcmcpher/my-skills --skill silent-failure-hunter-bcmcpher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and improve error handling by surfacing silent failures, ensuring errors are logged, actionable, and visible to users.

Core Features & Use Cases

Locate all error-handling blocks (try/catch, error callbacks, result unwraps) and verify they surface failures.
Evaluate logging quality, contextual information, and user-facing messages to provide actionable guidance.
Check error propagation and fallbacks to prevent silent masking of problems across modules, services, and UI.
Provide remediation recommendations and guardrails for production-grade reliability.

Quick Start

Run an audit on your codebase to identify silent failures and propose concrete remediation steps.

Frequently Asked Questions about silent-failure-hunter

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

FAQPage Schema

How do I find silent failures in my codebase?▼

To find silent failures, audit all error-handling blocks like try/catch and error callbacks to verify they surface failures. This process evaluates logging quality and checks error propagation to prevent silent masking of problems across modules.

What is a silent failure in error handling?▼

A silent failure in error handling occurs when catch blocks, error callbacks, or fallback logic mask problems without logging context or user feedback. This prevents errors from bubbling up appropriately and hides issues across services and UI components.

What's the best way to audit catch blocks for meaningful logging?▼

The best way to audit catch blocks is to enforce technical checks for specific catch types, verify logs contain meaningful context, and ensure explicit user guidance. This validates that fallbacks are justified and failures bubble up when appropriate.

How do I check if my fallback logic is masking errors?▼

To check if fallback logic is masking errors, review error propagation across modules and services to ensure fallbacks are explicitly justified. This validates that failures bubble up when appropriate instead of silently masking problems.

Can I audit error handling across UI components and services?▼

Yes, you can audit error handling across UI components and services. The scope covers codebases with error handling, logging, and fallback logic, ensuring reviews evaluate catch blocks, log messages, user feedback, and error propagation.

Why does my error handling not provide actionable user guidance?▼

Error handling lacks actionable user guidance when catch blocks fail to surface meaningful logs with context or explicit user-facing messages. Auditing evaluates logging quality to provide actionable remediation recommendations and production-grade reliability guardrails.