mcpField
G
git-guardrails-claude-code

git-guardrails-claude-code

github.com/polya20Agent workflows042 installsUpdated 24w ago
Repository

About git-guardrails-claude-code

A Claude Code skill that installs a PreToolUse hook to block selected destructive Git commands. It supports project-level or global setup and lets users customize the blocked patterns.

Key features

  1. 01Blocks selected destructive Git commands
  2. 02Installs a PreToolUse hook
  3. 03Supports project or global scope
  4. 04Allows customizing blocked patterns
  5. 05Includes a verification test

Use cases

  1. 01Preventing accidental pushes or hard resets
  2. 02Applying Git safeguards across projects
  3. 03Tailoring blocked commands to a workflow

Install

Copy the command and run it in a terminal.

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

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

Bundled filesscripts/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 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