Overview
Error handling reviews fail when they only check that try-catch blocks exist — not whether errors are being handled correctly within them. A catch block that logs the error and returns undefined has handled the error syntactically but silently changed the function's return type — callers expecting a value receive undefined and may proceed as if the operation succeeded. Error handling must be evaluated for what happens after the catch, not just whether a catch exists.
The Error Handling Code Review Framework identifies swallowed errors, missing context, incorrect error propagation, and the logging gaps that make production incidents invisible.