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.
A review skill for error handling robustness across the full stack.
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.
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.
Always log errors with structured context: user ID, request ID, input data, stack trace. An error message like "Cannot read property of undefined" with no context is impossible to debug — you don't know which user hit it, what they were doing, or how to reproduce it.
BeforeMerge scans your pull requests against all 2 Error Handling Review rules automatically. Get actionable feedback before code ships.