Iron Law: An empty catch block is not error handling — it is a lie to the operator. Every catch must log AND rethrow or return an error state.

Silent Failure Hunter

Enforces the "No Silent Failures" rule from code-standards.md — every catch block must log the error AND either rethrow or return an explicit error state. Finds swallowed exceptions, fallbacks that hide failures, and mock data returned on error.

When to Use

• After implementing features with API calls or database operations
• Reviewing any code that has try/catch blocks
• Before merging code that touches external service integrations
• Proactively after implementing I/O-heavy features

Forbidden Patterns (all languages)

catch (e) { return []; }           // Silent empty return
catch (e) { return MockData.x; }   // Fake data on failure
catch (e) { /* nothing */ }        // Swallowed exception
catch (e) { log.error(e); }        // Log only, no rethrow

Required Pattern

catch (e) {
  logger.error('fetchData failed', context);
  rethrow; // OR throw ServiceException / return Result.failure
}

Stack-Specific Patterns to Grep

Severity Levels

Output Format

## Silent Failure Audit: [scope]

### CRITICAL
[file:line] — [description of silent failure]
Hidden errors: [types that could be suppressed]
Fix: [corrected code]

### Summary
- Issues: N (critical: X, high: Y, medium: Z)
- Verdict: PASS / FAIL