{"version":"2.1.268","anchor":"new-git-safety-instruction-in-the-commitpr-prompt-template","canonical_anchor":"new-git-safety-instruction-in-the-commitpr-prompt-template","heading":"New git-safety instruction in the commit\/PR prompt template: avoid bulk git add","tier":"notice","area":"Git Safety","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/new-git-safety-instruction-in-the-commitpr-prompt-template","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### New git-safety instruction in the commit\/PR prompt template: avoid bulk `git add`\n\nCommit\/PR guidance now warns against bulk `git add -A` or `git add .`\n\n**What**\n\nThe built-in guidance Claude Code follows when committing changes or creating pull requests now includes a warning to stage files by name rather than using `git add -A` or `git add .`.\n\n**Why**\n\nBulk-adding all files can accidentally sweep in things like `.env` files, credentials, or large binary files that shouldn't be committed; staging specific files by name avoids that risk.\n\n- Area: Git Safety\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}