{"version":"2.1.196","anchor":"git-destructive-command-target-analysis","canonical_anchor":"git-destructive-command-target-analysis","heading":"Git Destructive Command Target Analysis","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.196\/e\/git-destructive-command-target-analysis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.196","markdown":"### Git Destructive Command Target Analysis\n\nWhen Claude analyzes destructive git commands for permission prompts, it now identifies the specific target to provide more contextually accurate warnings:\n\n- `git push --force`: identifies remote, refspec, and whether the target looks like a main-like branch.\n- `git reset --hard`: classifies the target as bare (no target), HEAD-relative, remote ref, or other.\n- `git branch -D`: detects whether the branch being deleted is a main-like protected branch.\n- `git commit --amend`: distinguishes `--no-edit`, `--message`\/`-m`, or interactive (opens editor).\n\n**Evidence**\n\nNew git target parsers (search for `\"git-destructive-target parse failed\"`)"}