reviewing-silent-failures
Silent failure detection patterns for frontend code. Triggers: サイレント障害, silent failure, 空のcatch, empty catch, 未処理Promise, unhandled rejection, unhandled promise, Error Boundary, fire and forget, エラーハンドリング, error handling, try-catch.
When & Why to Use This Skill
This Claude skill specializes in identifying silent failure patterns within frontend codebases. It proactively detects swallowed errors, empty catch blocks, and unhandled promises that often lead to difficult-to-debug production issues, ensuring more robust and maintainable error-handling logic.
Use Cases
- Automated Code Audits: Scanning repositories to identify and refactor 'empty catch' blocks or console-only error logging that hides critical failures from developers and monitoring tools.
- Asynchronous Logic Validation: Detecting unhandled Promise rejections and missing .catch() chains in complex frontend workflows to prevent application hangs or inconsistent states.
- UI Resilience Enhancement: Identifying missing Error Boundaries and silent fallbacks (like nullish coalescing without telemetry) to ensure users receive proper feedback when components fail.
| name | reviewing-silent-failures |
|---|---|
| description | > |
| allowed-tools | [Read, Grep, Glob, Task] |
| agent | silent-failure-reviewer |
| context | fork |
| user-invocable | false |
Silent Failure Review
Detection
| ID | Pattern | Fix |
|---|---|---|
| SF1 | catch (e) {} |
catch (e) { logger.error(e); throw } |
| SF1 | catch (e) { console.log(e) } |
Show user feedback + log context |
| SF2 | .then(fn) without .catch() |
Add .catch() or use try/catch |
| SF2 | async () => { await fn() } |
Wrap in try/catch, handle error |
| SF3 | No error UI states | Add error boundary, feedback component |
| SF4 | value ?? defaultValue silently |
Log when using fallback |
| SF4 | data?.nested?.value |
Check and report if unexpected null |
References
| Topic | File |
|---|---|
| Detection | references/detection-patterns.md |