{"version":"2.1.277","anchor":"write-tools-dangerous-rm-on-unset-variable-check-refactored","canonical_anchor":"write-tools-dangerous-rm-on-unset-variable-check-refactored","heading":"Write tool's dangerous-rm-on-unset-variable check refactored, message likely unchanged","tier":"internal","area":"Bash Safety","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/write-tools-dangerous-rm-on-unset-variable-check-refactored","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Write tool's dangerous-rm-on-unset-variable check refactored, message likely unchanged\n\nInternal cleanup of the dangerous rm-with-unset-variable safety check, no visible behavior change\n\n**What**\n\nThe safety check that warns about bash commands like `rm -rf $UNSET\/*` (deleting based on a variable that might be empty or unset) now builds its warning message through a shared helper function instead of assembling the text inline. The check still fires under the same internal event name, `tengu_bash_dangerous_rm_too_complex`.\n\n**Why**\n\nThis is an internal refactor; the warning shown to users for this kind of risky command is expected to stay the same.\n\n- Area: Bash Safety\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}