mcpField
G
git-guardrails-claude-code

git-guardrails-claude-code

github.com/mattpocockDevelopment305.7k513.0k installsUpdated 1d ago
Repository

About git-guardrails-claude-code

git-guardrails-claude-code is a skill that sets up a PreToolUse hook to block dangerous git commands before Claude runs them. It can be installed for one project or globally, and it merges into existing settings. It suits users who want to limit destructive git operations.

Key features

  1. 01Blocks git push, including forced variants
  2. 02Blocks git reset --hard and git clean -f
  3. 03Blocks git branch -D and discarding checkout or restore
  4. 04Installs per project or globally
  5. 05Merges into existing settings without overwriting

Use cases

  1. 01Preventing a coding agent from pushing to a remote
  2. 02Restricting destructive git cleanup commands in Claude
  3. 03Applying git safety hooks across a team project

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mattpocock/skills --skill git-guardrails-claude-code

After installing, type/git-guardrails-claude-codein Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlscripts/block-dangerous-git.sh

Details

From the project README

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

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

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

Comments

Markdown supported