Git Guardrails Claude Code

by mattpocockc55ee46073edNo licenseListed Oct 8, 2026Updated Oct 8, 2026

Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

Includes scriptsSecurity AI & Agents

AI-generated overview

Sets up Claude Code hooks that block dangerous git commands such as push, reset --hard and clean before they run.

What it does: This skill installs a PreToolUse hook in Claude Code that intercepts Bash tool calls and blocks destructive git commands, including git push, git reset --hard, git clean -f/-fd, git branch -D and git checkout ./git restore . It copies a bundled shell script into a project-level or global hooks directory, makes it executable, and merges the hook entry into the relevant settings file without overwriting existing settings. It also offers to customize the blocked pattern list and provides a test command to verify the hook exits with code 2 and prints a BLOCKED message.
When to use it: Use it when you want to prevent Claude Code from running destructive git operations, add git safety hooks, or block git push and reset commands in an agent session. It fits users who want guardrails at either project scope or across all projects.
Requirements: Requires Claude Code with hook support and a writable settings file (.claude/settings.json or ~/.claude/settings.json). It ships an executable shell script (scripts/block-dangerous-git.sh) and needs a POSIX shell environment with chmod; no credentials or network access are required.

Setup Git Guardrails

Sets up a PreToolUse hook that intercepts and blocks dangerous git commands before Claude executes them.

What Gets Blocked

git push (all variants including --force)
git reset --hard
git clean -f / git clean -fd
git branch -D
git checkout . / git restore .

When blocked, Claude sees a message telling it that it does not have authority to access these commands.

Steps

1. Ask scope

Ask the user: install for this project only (.claude/settings.json) or all projects (~/.claude/settings.json)?

2. Copy the hook script

The bundled script is at: scripts/block-dangerous-git.sh [blocked]

Copy it to the target location based on scope:

Project: .claude/hooks/block-dangerous-git.sh
Global: ~/.claude/hooks/block-dangerous-git.sh

Make it executable with chmod +x.

3. Add hook to settings

Add to the appropriate settings file:

Project (.claude/settings.json):

json

{  "hooks": {    "PreToolUse": [      {        "matcher": "Bash",        "hooks": [          {            "type": "command",            "command": "\"$CLAUDE_PROJECT_DIR\"/.claude/hooks/block-dangerous-git.sh"          }        ]      }    ]  }}

{  "hooks": {    "PreToolUse": [      {        "matcher": "Bash",        "hooks": [          {            "type": "command",            "command": "\"$CLAUDE_PROJECT_DIR\"/.claude/hooks/block-dangerous-git.sh"          }        ]      }    ]  }}

Global (~/.claude/settings.json):

json

{  "hooks": {    "PreToolUse": [      {        "matcher": "Bash",        "hooks": [          {            "type": "command",            "command": "~/.claude/hooks/block-dangerous-git.sh"          }        ]      }    ]  }}

{  "hooks": {    "PreToolUse": [      {        "matcher": "Bash",        "hooks": [          {            "type": "command",            "command": "~/.claude/hooks/block-dangerous-git.sh"          }        ]      }    ]  }}

If the settings file already exists, merge the hook into the existing hooks.PreToolUse array. Don't overwrite other settings.

4. Ask about customization

Ask if user wants to add or remove any patterns from the blocked list. Edit the copied script accordingly.

5. Verify

Run a quick test:

Should exit with code 2 and print a BLOCKED message to stderr.

Source and attribution

Source:mattpocock/skillsinskills/misc/git-guardrails-claude-codeat commitc55ee46

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Git Guardrails Claude Code

Setup Git Guardrails

What Gets Blocked

Steps

1. Ask scope

2. Copy the hook script

3. Add hook to settings

4. Ask about customization

5. Verify

Source and attribution

More from mattpocock/skills

Chief Of Staff

Writing For Agents

Wait What

To Questionnaire

Teach

Handoff

More in Security

Secops Triage

Secops Investigate

Secops Hunt

Secops Cases

Iam Helper For Policy Management

Gke Workload Security