block-no-verify-hook

PreToolUse hook configuration that intercepts and blocks bypass-flag usage before execution, ensuring AI agents cannot skip pre-commit hooks, GPG signing, or other git safety mechanisms. AI coding agents (Claude Code, Codex, etc.) can run shell commands with flags like --no-verify that bypass pre-commit hooks. This defeats the purpose of linting, formatting, testing, and security checks configured in pre-commit hooks. The block-no-verify hook adds a PreToolUse guard that rejects any tool call containing bypass flags before execution. When AI agents commit code, they may use bypass flags to avoid hook failures: This allows: Add a PreToolUse hook to .claude/settings.json that inspects every Bash tool call and blocks commands containing bypass flags. Add the following to your project's .claude/settings.json : Create or update .claude/settings.json in your project root: To enforce across all projects, add to ~/.claude/settings.json : Test that the hook blocks bypass flags: To block additional flags (e.g., --force ), extend the grep pattern: The block-no-verify hook works alongside other PreToolUse hooks: - Unformatted code to enter the repository - Linting errors to bypass checks - Security scanning to be skipped - Unsigned commits to bypass signing policies - Test suites to be circumvented - Matcher : The hook targets only Bash tool calls, so it does not interfere with other...