{"version":"2.1.323","anchor":"prompt-shell-commands-that-run-git-withhold-allow-rules","canonical_anchor":"prompt-shell-commands-that-run-git-withhold-allow-rules","heading":"Skill shell commands that run git no longer use your always-allow rules","tier":"notice","area":"Skills","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/prompt-shell-commands-that-run-git-withhold-allow-rules","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Skill shell commands that run git no longer use your always-allow rules\n\nWhen a skill's built-in shell command uses git, Claude Code checks it without your always-allow rules and may ask or refuse\n\n**Unclear.** It is not clear whether this stricter check is switched on by default.\n\n**What**\n\nA skill can include shell commands that run as part of its instructions. When such a command involves git, Claude Code now checks its permission without your always-allow rules for commands and without the skill's own list of allowed tools.\n\nIf the command cannot pass that stricter check, you see a message that a file named HEAD or .git in this folder or one above it may not be yours.\n\n**Why**\n\nThis guards against a folder you opened that contains planted git files meant to make git do something harmful. Skills that run git may now ask for permission or fail where they used to run quietly.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}