overcautious-check

To detect silent error swallowing in recent git changes, scan source code for empty catch blocks, unauthorized fallbacks, and suppressed test or lint failures. Categorize findings into BLOCK, WARN, and INFO to prioritize security and stability issues.

Silent error swallowing is the practice of masking failures through empty catch blocks or unauthorized fallbacks. It affects code stability by preventing bugs from surfacing, violating robust error-handling policies, and hiding network failures or security bypasses behind graceful degradation.

To check for empty catch blocks and unauthorized fallbacks during a code review, analyze recent git changes for patterns that silence or hide failures. Ensure strict error propagation by performing full-file context analysis against project error handling rules.

Yes, you can scan recent git commits for suppressed linting or test failures. The analysis targets recent changes to identify hidden error handling patterns, categorizing suppressed failures by severity to highlight critical security and stability issues.

Yes, this static analysis tool requires access to project error handling rules to function accurately. It uses these rules alongside full-file context analysis to identify unauthorized fallbacks and ensure strict error propagation across recent git changes.

You should avoid using graceful degradation in error handling when it hides network failures or security bypasses. If recent git changes introduce unauthorized fallbacks that prevent bugs from surfacing, they violate robust error propagation policies and should be flagged.