Error Handling

v1.0.0

Reviews error handling patterns — error boundaries, structured logging, graceful degradation, and user-facing error communication. Silent failures and swallowed exceptions are the leading cause of "it works on my machine" bugs that only surface in production.

2 rules

1 categories

Quality(2)

Use Error Boundaries

Wrap UI sections in React Error Boundaries to catch rendering errors gracefully. Without error boundaries, a single component crash (a null reference, a failed API parse) takes down the entire page — showing users a white screen with no way to recover or navigate away.

ReactqualityError Boundaries

HIGH

Automate Error Handling checks on every PR

BeforeMerge scans your pull requests against all 2 Error Handling rules automatically. Get actionable feedback before code ships.

Join Waitlist Browse All Rules

Error Handling Review

A review skill for error handling robustness across the full stack.

What it covers

Error boundaries — React error boundaries, global exception handlers, process-level crash recovery
Structured logging — consistent error format, correlation IDs, severity levels, no sensitive data in logs
Graceful degradation — fallback UI states, partial failure handling, circuit breaker patterns
Error propagation — when to catch vs. rethrow, wrapping errors with context, typed error hierarchies
User communication — actionable error messages, retry affordances, distinguishing user errors from system errors
Async error handling — unhandled promise rejections, try/catch in async functions, timeout handling

When to use

Run this on any PR that adds new API calls, modifies error paths, or introduces failure-prone operations like file I/O, network requests, or database transactions.