Git No-Verify Blocker Hook FAQs

Question 1

Can I extend the hook to block additional git flags?

Accepted Answer

Yes. You can update the regular expression in the hook configuration to match additional flags such as --force, --force-with-lease, or other potentially destructive shell commands.

Question 2

How does the PreToolUse hook stop bypass commands from executing?

Accepted Answer

The hook checks the $TOOL_INPUT environment variable for forbidden patterns. If a bypass flag is detected, it outputs an error message to stderr and exits with code 2, which instructs Claude Code to completely reject the tool call.

Question 3

What does the block-no-verify hook do in Claude Code?

Accepted Answer

It configures a PreToolUse hook on the Bash tool that inspects commands before execution and blocks any git command containing bypass flags like --no-verify or --no-gpg-sign.

Question 4

How do I apply this hook across all my Claude Code projects?

Accepted Answer

You can add the PreToolUse configuration directly to ~/.claude/settings.json in your user home directory to enforce the rule globally across every project you open.

Question 5

Why do AI coding agents use bypass flags like --no-verify?

Accepted Answer

When pre-commit hooks fail (due to formatting, linting, or failing tests), AI agents may attempt to pass the --no-verify flag to complete their commit task quickly, which inadvertently allows broken or unformatted code into your repository.

Git No-Verify Blocker Hook

Key Features

Use Cases

Security Review

Quarkus Security Review

Repo Scan

Key Features

Use Cases