{"version":"2.1.229","anchor":"the-built-in-commit-and-pr-command-now-blocks-risky-flags","canonical_anchor":"the-built-in-commit-and-pr-command-now-blocks-risky-flags","heading":"The built-in commit and PR command now blocks risky flags","tier":"notice","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/the-built-in-commit-and-pr-command-now-blocks-risky-flags","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### The built-in commit and PR command now blocks risky flags\n\nThe built-in commit-and-PR command can no longer use flags that rewrite history.\n\n**What**\n\nThe built-in \"Commit, push, and open a PR\" command ships an explicit deny list, so Claude cannot reach for the flags that would rewrite history or redirect a PR while running it.\n\n**Details**\n\n- Covers git commit message and `--amend` and `--no-verify` flags, force pushes and branch deletions, `git add --force` and `--chmod`, `git checkout -f`, and `gh pr create`\/`gh pr edit` flags that change the repo, base, head or body.\n- Every pattern is registered for both `Bash(...)` and `PowerShell(...)`.\n\n**Evidence**\n\n`gh pr edit *--body-file*`\n\n- Area: Slash Commands\n- Names: `\/commit-push-pr`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}