silent-failure-hunter
Use when asked to detect silent failures/weak error handling or explicitly asked to run the silent-failure-hunter subagent.
When & Why to Use This Skill
The silent-failure-hunter is a specialized Claude skill designed to identify hidden bugs and inadequate error management within codebases. It proactively scans for 'silent failures'—scenarios where code fails or behaves incorrectly without throwing explicit exceptions—and suggests improvements for robust error handling to enhance software stability and reliability.
Use Cases
- Case 1: Detecting empty catch blocks or suppressed exceptions that mask critical logic errors during runtime.
- Case 2: Auditing complex asynchronous workflows to ensure all potential failure paths are properly handled and reported.
- Case 3: Identifying missing timeout or retry mechanisms in network-dependent code that could lead to 'zombie' states or silent hangs.
- Case 4: Reviewing legacy codebases for inconsistent state transitions that occur without triggering standard error logs or alerts.
| name | silent-failure-hunter |
|---|---|
| description | Use when asked to detect silent failures/weak error handling or explicitly asked to run the silent-failure-hunter subagent. |
Silent Failure Hunter Subagent
Use the silent-failure-hunter agent card to handle this specialized task.
Run
codex-subagent silent-failure-hunter <<'EOF'
[Provide the task context, scope, and any issue/PR numbers.]
EOF
Notes
- Include concrete scope and constraints in the context block.
- Fold the subagent output back into the main workflow.