git-guardrails

To block unsafe git commands, you can enforce harness-level safety checks using a configurable guard script. It rejects dangerous operations before execution by reporting a BLOCKED message and exiting with code 2.

Preventing accidental git checkout . across multiple repositories is achieved by wiring a guard script into the PreToolUse Bash hooks. This enforces workflow security and rejects destructive commands before they run.

Configuring PreToolUse Bash hooks for git safety requires wiring the guard script into .claude/settings.json. Once active, the harness inspects git commands and blocks unsafe operations across developer workflows.

Yes, you can run smoke tests to verify blocked git commands. The harness guard script ensures unsafe operations produce a BLOCKED message and exit with code 2, confirming the safety checks are active.

You can customize the git safety guard script by modifying the file at .claude/hooks/guards/git-guardrails.sh. This allows you to inspect, troubleshoot, and tailor the specific unsafe git operations to block.

Using harness-level hooks for workflow security requires the guard script to be correctly wired into .claude/settings.json. It relies on the PreToolUse Bash hooks to intercept commands, meaning any git operations bypassing this harness will not be blocked.