error-handling-review

Error handling review identifies swallowed failures by flagging overly broad exception catching and unchecked cleanup returns, ensuring errors are never silently lost. It categorizes findings by domain, validation, infrastructure, programming, and cancellation semantics.

Exception taxonomy in code review categorizes errors into domain, validation, infrastructure, programming, and cancellation groups. This categorization ensures review recommendations match the specific failure meaning, preventing incorrect error semantics and weak wrapping across multi-language implementations.

Resilience review evaluates retry backoff quality, circuit breaker implementation, timeout coverage, and partial failure semantics. It also checks dead-letter queue strategy for poison messages and user-facing error message quality to prevent confusing outages.

Yes, error handling review applies across batch workflows, API user-facing errors, and multi-language implementations. It evaluates timeout coverage, cancellation behavior, and partial failure semantics to ensure failures do not become silent corruption or dead ends.

Common error handling anti-patterns include swallowed errors, overly broad exception handling, lost context, weak wrapping, and unchecked cleanup returns. Reviewing for these language-specific mistakes prevents silent data corruption and confusing user-facing dead ends.

Error handling review findings are graded by severity into Blocking, Recommendation, and Observation groups. Each actionable finding must cite the violated taxonomy category, ensuring review items are tied to explicit error semantics and resilience requirements.