{"version":"2.1.269","anchor":"bash-tool-prompt-drops-explicit-git-safety-guidance-paragrap","canonical_anchor":"bash-tool-prompt-drops-explicit-git-safety-guidance-paragrap","heading":"Bash tool prompt drops explicit git-safety guidance paragraph, replaced by an injected variable","tier":"notice","area":"Bash Tool","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/bash-tool-prompt-drops-explicit-git-safety-guidance-paragrap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Bash tool prompt drops explicit git-safety guidance paragraph, replaced by an injected variable\n\nBash tool's built-in git-safety guidance paragraph removed, replaced by an injected variable\n\n**Unclear.** What the injected `${m}` value actually contains, and whether it preserves the same git-safety guidance, isn't shown by this finding.\n\n**What**\n\nThe description given to the model for the Bash tool used to end with a fixed paragraph telling it to prefer creating new git commits over amending existing ones, and warning against destructive git operations and skipping hooks or commit signing. That fixed paragraph has been removed and replaced with a value that gets filled in elsewhere in the code.\n\n**Why**\n\nThe git-safety guidance the model receives for Bash commands is now assembled dynamically rather than hardcoded in the tool description, though what content actually gets substituted in is not shown here.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}