codeprobe-error-handling

Standalone Mode

If invoked directly (not via the orchestrator), you must first:

1. Read ../codeprobe/shared-preamble.md (resolve relative to this SKILL.md's location — the sibling codeprobe skill directory — not the user's project) for the output contract, execution modes, and constraints.
2. Load applicable reference files from ../codeprobe/references/ (same resolution) based on the project's tech stack.
3. Default to full mode unless the user specifies otherwise.

Error Handling & Resilience Checker

Domain Scope

This sub-skill detects error handling and resilience issues across these categories:

1. Swallowed Exceptions — Empty catch blocks, catch-and-log-only without rethrow/handle
2. Missing Error Handling — External API calls without try/catch, unhandled promise rejections
3. Error Information — Generic error messages, leaking internals, missing structured responses
4. Retry & Circuit Breaker — No timeout on external calls, no retry for transient failures
5. Validation — Missing input validation, implicit null assumptions, type coercion bugs
6. Transaction Safety — Multi-step DB operations without transactions, missing rollback
7. Logging — No logging on critical paths, missing correlation IDs

---

What It Does NOT Flag

• Sensitive data in logs — covered by codeprobe-security (SEC prefix). This sub-skill flags missing logging and structural issues like no correlation IDs, not data leakage.
• Test files — test exception handling follows different patterns and is expected to be simpler.
• Framework-generated exception handlers (e.g., Laravel's Handler.php, Next.js error boundaries that are intentionally minimal) — these are scaffolded defaults, not developer oversights.
• CLI scripts with intentionally simple error handling (print + exit) — command-line tools often use a valid pattern of printing an error and exiting with a non-zero code.
• Catch blocks that deliberately swallow specific known-harmless exceptions with a comment explaining why — if the developer documented the rationale, respect the decision.
• Issues that are primarily security vulnerabilities (e.g., authentication bypasses, injection, data exposure) even if they also have error handling implications — these are covered by codeprobe-security. If both sub-skills flag the same location, the orchestrator will deduplicate and keep the security finding as primary.