block-no-verify-hook

To prevent git commit bypass flags in Claude Code, use a PreToolUse hook that inspects Bash tool input and rejects commands containing --no-verify or --no-gpg-sign before execution. This enforces pre-commit and signing policies at the source.

Git bypass flags like --no-verify and --no-gpg-sign skip pre-commit hooks and commit signing protections. Blocking them in pre-commit hooks maintains repository governance, quality gates, and commit integrity in AI-assisted workflows.

To set up a PreToolUse hook to block --no-verify, add a Bash matcher to your Claude Code settings that inspects TOOL_INPUT for git commands and rejects any execution containing unsafe override flags before the command runs.

Yes, this git hook bypass protection works with existing repository governance policies by ensuring commit-msg, pre-commit, and signing checks still run. It enforces consistent repository hygiene in team environments without altering existing workflows.

Yes, you can use this to stop AI agents from skipping commit signing in team environments. It scans Bash tool calls for --no-gpg-sign flags and blocks execution, ensuring commit signing protections remain active across all team workflows.

When a git command with a bypass flag is detected, the command is rejected early before execution. This early rejection ensures pre-commit, commit-msg, and signing policies still run, preventing hidden bypasses from weakening quality gates.