block-no-verify-hook

Block git bypass flags with a PreToolUse hook in .claude/settings.json.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/Sumeet138/qwen-code-agents --skill block-no-verify-hook-sumeet138
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: block-no-verify-hook
Source: https://github.com/Sumeet138/qwen-code-agents/tree/main/plugins/block-no-verify/skills/block-no-verify-hook
Command: npx skills add https://github.com/Sumeet138/qwen-code-agents --skill block-no-verify-hook-sumeet138

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure a PreToolUse hook to prevent AI agents from skipping git pre-commit hooks with --no-verify and other bypass flags. Use when setting up Claude Code projects that enforce commit quality gates.

Core Features & Use Cases

  • Intercepts and blocks bypass-flag usage before execution to ensure pre-commit hooks, GPG signing, and other safety checks cannot be bypassed.
  • Provides per-project configuration guidance and a ready-to-install .claude/settings.json Hook.
  • Works across AI coding pipelines (Claude Code and similar agents) to enforce repository-level quality gates during automated tasks.

Quick Start

Add a .claude/settings.json with a PreToolUse Bash hook that blocks --no-verify and --no-gpg-sign in git commands.

Frequently Asked Questions about block-no-verify-hook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent AI coding agents from bypassing git pre-commit hooks with --no-verify?

To prevent AI agents from bypassing git pre-commit hooks, configure a PreToolUse hook that intercepts and blocks --no-verify flags before command execution. This ensures automated workflows cannot skip repository quality gates.

What is a PreToolUse hook and how does it enforce commit signing in Claude Code?

A PreToolUse hook is a JSON configuration in .claude/settings.json that inspects commands before execution. It enforces commit signing by blocking bypass flags like --no-gpg-sign, ensuring safety checks always run.

How do I set up a .claude/settings.json file to block --no-verify and --no-gpg-sign flags?

Set up a .claude/settings.json file by adding a PreToolUse Bash hook that targets and blocks bypass flags. This provides per-project enforcement against --no-verify and --no-gpg-sign in git commands.

Does this pre-commit hook enforcement work across different AI-driven coding workflows?

Yes, this pre-commit hook enforcement works across AI coding pipelines like Claude Code and similar agents. It applies per-project configuration to ensure repository-level quality gates run during automated tasks.

Why does my AI agent keep skipping GPG signing when executing automated git commits?

AI agents skip GPG signing by executing git commands with the --no-gpg-sign flag. Blocking this bypass flag via a PreToolUse hook forces the agent to execute commits with signing checks intact.