Catches the mistakes coding agents repeat before they merge: a pull-request gate with no model call and no API key.
Short answer: Log or surface errors; never use empty catch blocks. An error that is swallowed leaves no trace, so a failure looks like success.
Group: Reliability and fallbacks. Status: stable. Generated from the rule definitions; do not edit by hand.
Playground: https://brevio.pro/tools/agent-guard-playground?rule=R5.4
No silent exception swallowing: log or surface errors; never use empty catch blocks.
An error that is swallowed leaves no trace, so a failure looks like success.
try { await save(); } catch (e) {}
try { await save(); } catch (e) { log.error('save failed', e); throw e; }
brevio-core scan: a scan of added lines (code_rules.scan_added_lines_for_rules).dev_rules.slice_micro_rules).A person can silence one finding with brevio-core: ignore R5.4 -- reason on the line or the line above. Without the reason it does not count. An agent cannot silence it: the agent hook and the MCP tools never honour the comment, and a pull request that adds one is reported until a reviewer allows it. Fixing the code is still the better answer.
A scan reads only the lines you add, so a line that was already in the file is not flagged.
To change what the rule flags, edit its definition in dev_rules.py or code_rules/__init__.py. That is a code change and is reviewed like one.