block-no-verify

Block Git commits and pushes that use --no-verify to bypass pre-commit hooks.

3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill block-no-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: block-no-verify
Source: https://github.com/vtgiang-dotcom/Solo-Code-Harness/tree/main/.gemini/antigravity/skills/block-no-verify
Command: npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill block-no-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents git commits that bypass pre-commit hooks by blocking --no-verify usage during commit or push operations.

Core Features & Use Cases

  • Detects bypass attempts such as git commit --no-verify, git commit -n, git push --no-verify, and git am --no-verify.
  • Blocks the operation and provides guidance to perform a proper commit with pre-commit hooks.
  • Logs governance prompts for audit when bypass is approved.

Quick Start

When a bypass attempt is detected, block the operation and prompt for a normal commit with pre-commit hooks.

Frequently Asked Questions about block-no-verify

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

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

You can prevent git commit --no-verify bypasses by using a workflow that detects --no-verify and -n flags, blocks the operation, and prompts for a proper commit with pre-commit hooks enabled.

What is the best way to enforce strict code quality and block git push --no-verify?

The best way to block git push --no-verify is implementing detection for bypass attempts that stops the push and guides developers to execute a safe alternative workflow with hooks active.

Why does git commit -n bypass my pre-commit security checks?

Git commit -n bypasses pre-commit security checks because it is a shorthand alias for --no-verify, which natively instructs Git to skip all hook execution during that specific commit operation.

Can I log governance audit trails when a pre-commit hook bypass is approved?

Yes, you can log governance prompts for audit by configuring the block-no-verify workflow to record when a bypass is approved, ensuring strict code quality enforcement and traceability.

Does blocking git am --no-verify help enforce local commit quality standards?

Blocking git am --no-verify enforces local commit quality standards by preventing mail-based patch applications from skipping hooks, ensuring all applied changes pass required lint checks.