Skip to content

jupes/agent-forge-harness / .agents/skills/git-guardrails-claude-code

git-guardrails-claude-code

Verified

Install or review a Claude Code hook for blocking selected Git commands. Use when the user requests Git safety guardrails.

FileKindSize
SKILL.mdskill md4.6 KB
references/block-dangerous-git.sh.mdmarkdown1.8 KB
---
name: git-guardrails-claude-code
description: Install or review a Claude Code hook for blocking selected Git commands. Use when the user requests Git safety guardrails.
---

# git-guardrails-claude-code

Guide a user through installing a Claude Code `PreToolUse` hook that blocks dangerous git commands before they execute.

This Agent Forge port is guidance-first: do not install hooks, edit `.claude/settings.json`, edit `~/.claude/settings.json`, or create executable hook files unless the user explicitly asks for installation in the current task.

The bundled reference needs Bash, jq, and grep. Its regex matching is a convenience guard,
not a shell parser or security boundary; aliases and alternate command forms can bypass it.
Test candidate commands as JSON input without executing them. Prefer an existing repository
hook when it already implements the requested policy.

## What gets blocked

The reference hook blocks commands matching these patterns:

- `git push`, including force-push variants
- `git reset --hard`
- `git clean -f` and `git clean -fd`
- `git branch -D`
- `git checkout .`
- `git restore .`
- Short forms that still contain `push --force` or `reset --hard`

When a command is blocked, the hook exits with code `2` and prints a message explaining which dangerous pattern matched.

## Workflow

### 1. Confirm scope

Use the requested scope. If no scope is specified, ask whether the guardrail belongs in the project or globally:

- **Project only**: `.claude/settings.json` with the hook script under `.claude/hooks/block-dangerous-git.sh`
- **Global**: `~/.claude/settings.json` with the hook script under `~/.claude/hooks/block-dangerous-git.sh`

If the user only asks for advice or review, provide the guidance and stop before editing files.

### 2. Review the reference hook

Use the bundled reference as the source for the script content:

[references/block-dangerous-git.sh.md](references/block-dangerous-git.sh.md)

Keep it as documentation unless installation is explicitly requested. If installing, copy the shell script content from the reference into the selected hook path and make that copied file executable.

```bash
chmod +x .claude/hooks/block-dangerous-git.sh
```

For global installs, use the global hook path instead:

```bash
chmod +x ~/.claude/hooks/block-dangerous-git.sh
```

### 3. Merge hook settings

Add a `PreToolUse` hook for the Bash tool. If the settings file already exists, merge into the existing JSON and preserve all unrelated settings and hooks.

Project-scoped hook:

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

Global hook:

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

Do not replace an existing `hooks.PreToolUse` array. Append the new command hook only if an equivalent command is not already present.

### 4. Customize intentionally

Use the requested blocked-command policy. Explain the defaults and ask only if they conflict with the repository's workflow; ordinary push is required by Forge session completion.

Common customizations:

- Allow ordinary `git push` but keep blocking `git push --force`.
- Add `git checkout -- .` or repo-specific destructive commands.
- Add explanatory text that matches the team's git policy.

Document any customization in the response so future agents understand the local policy.

### 5. Verify with sample JSON

Test the installed or candidate script by piping Claude Code hook JSON into it:

```bash
echo '{"tool_input":{"command":"git push origin main"}}' | .claude/hooks/block-dangerous-git.sh
```

Expected result:

- Exit code: `2`
- Stderr includes `BLOCKED`
- Message includes the matched pattern, such as `git push`

Also test an allowed command:

```bash
echo '{"tool_input":{"command":"git status --short"}}' | .claude/hooks/block-dangerous-git.sh
```

Expected result:

- Exit code: `0`
- No block message

## Agent Forge safety notes

- Preserve non-interactive shell behavior; never run commands that wait for input.
- Do not run a real dangerous git command to test the hook.
- Do not install this hook as part of a porting or documentation task.
- Do not overwrite settings files. Parse and merge JSON when installation is requested.
- Keep project-specific installs in the target project, not in this harness, unless the user explicitly chooses this repository as the target.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall