--- name: mattpocock-git-guardrails-claude-code description: "Set up Claude Git command hooks." license: MIT metadata: source: mattpocock/skills source-commit: 4ae2317ddb22b046e26455e4f9c9b3aaaf62212d upstream-name: git-guardrails-claude-code upstream-status: published adaptation: namespaced-port --- ## Skillz integration This is Matt Pocock's version. Skill references use the `mattpocock-` prefix. Read a referenced skill's `SKILL.md` through the host's skill loader or file tools. Map AskUserQuestion to the host's question tool and shell examples to its shell. Use delegation only when available and permitted by the active instructions; otherwise perform the same work sequentially and report that limit. The user's scope and repository rules govern setup, file writes, tracker changes, messages, schedules, publishing, merging, and cleanup. A skill invocation alone does not broaden the user's request. Preserve existing work and configuration. Verify provider examples against current primary documentation before use. These hooks apply to Claude Code only. The matcher is a best-effort convenience, not a security boundary or a complete shell parser. Test the selected patterns before installing them. # 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](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`): ```json { "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" } ] } ] } } ``` 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: ```bash echo '{"tool_input":{"command":"git push origin main"}}' | ``` Should exit with code 2 and print a BLOCKED message to stderr.