mcpField
G
git-guardrails-claude-code

git-guardrails-claude-code

github.com/leandrocfeAgent workflows4182 installsUpdated 11w ago
Repository

About git-guardrails-claude-code

A skill that installs a Claude Code PreToolUse hook to block specified destructive Git commands. It supports project-level or global setup and allows the blocked patterns to be customized.

Key features

  1. 01Blocks specified dangerous Git commands
  2. 02Project-level or global installation
  3. 03Customizable blocked command patterns
  4. 04Verification test for the hook

Use cases

  1. 01Prevent accidental pushes from Claude Code
  2. 02Block destructive repository cleanup commands
  3. 03Apply Git restrictions across a project or globally

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/leandrocfe/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 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