git-guardrails-claude-codelisted

# Setup Git Guardrails Sets up a PreToolUse hook that intercepts and blocks dangerous git commands before Claude executes them, and refuses `gh pr merge` when the pull request's review stamp is stale. ## Invocation Position This is an infrastructure safety skill, not a feature-delivery step. Use `/git-guardrails-claude-code` when the project or user wants stronger protection against destructive git operations in Claude-driven workflows. Do not treat it as part of the normal feature pipeline. It is a repo or user setup action that makes later work safer. ## What Gets Blocked - `git push --force` / `git push -f` / `git push --force-with-lease` - `git push origin +main` (a leading `+` on a refspec is a force push) - `git push --mirror` (force-updates every remote ref) - `git reset --hard` - `git clean -f` / `git clean -fd` / `git clean -df` / `git clean -d -f` - `git branch -D` / `git branch --delete --force` / `git branch -f -d` - `git checkout .` / `git restore .` / `git checkout -- .` / `git restore -- .` - `git checkout ./` / `git checkout ./.` / `git checkout :/` / `git restore :/` The guard reads the command as tokens and never evaluates it, so a destructive command assembled at run time — a flag or subcommand held in a variable, spliced with `${IFS}`, or produced by command substitution — is not visible to it. That is a limit of the design, not a missing entry; #334 records it alongside the destructive commands the lists do not yet cover. ## What Gets Blocked Con