Skill

git-guardrails-claude-code

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.

npx claudepluginhub qhuang20/shazam --plugin shazam

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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

Supporting Assets

scripts/block-dangerous-git.sh

SKILL.md

Similar Skills

git-guardrails-claude-code

47.6k

Sets up Claude Code PreToolUse hooks to block dangerous git commands (push, reset --hard, clean, branch -D) before execution. Prevents destructive git ops in AI coding.

1 file

mattpocock-skills

hooks

Installs/uninstalls hooks in Claude Code that block raw git commands like 'git pull' and 'git checkout -b', enforcing git-town alternatives such as 'git town sync' and 'git town hack'.

1 file8 tools

git-town-workflow

cc-safe-setup

Installs 695 pre-built safety hooks for Claude Code preventing file deletions, credential leaks, git disasters, and token waste in autonomous AI coding sessions. Use for safe AI-driven development.

cc-safe-setup

Stats

Stars2

Forks0

Last CommitApr 6, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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

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):

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

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

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

If the settings file already exists, merge the hook into 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:

echo '{"tool_input":{"command":"git push origin main"}}' | <path-to-script>

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

What comes next

After guardrails are set up, suggest: "Git guardrails installed! You might also want /setup-pre-commit for commit-time linting."