block-no-verify-hook

by wshobson 39k MIT Updated Aug 5, 2026
Workflow Claude Code
block-no-verify-hook skill by wshobson
block-no-verify-hook — Workflow skill by wshobson

block-no-verify-hook is an open-source workflow skill for Claude Code, published by wshobson. Its author describes it as: “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.”. The project has 39k stars on GitHub and is available under the MIT license. Add it to your setup with `/plugin marketplace add wshobson/agents`.

Installation

Add block-no-verify-hook to your agent with:

/plugin marketplace add wshobson/agents

Always review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.

When to use it

Reach for block-no-verify-hook when you want workflow help from Claude Code without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.

Strengths

  • Clear MIT license — safe to read and adapt
  • Ships in wshobson/agents, an established project with 38,529 GitHub stars
  • Declares compatibility with Claude Code
  • Actively maintained (recent commits)

Topics

agent-skillsagentic-aiagentsai-agentsanthropicautomationclaude-codeclaude-code-pluginscodex-clicopilotcursorcursor-rulesdeveloper-toolsgemini-climcpmulti-agentopencodeorchestrationprompt-engineeringworkflows

Frequently asked questions

What does block-no-verify-hook do?
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.
How do I install block-no-verify-hook?
Run /plugin marketplace add wshobson/agents in your agent, then reload your skills. Review the source at https://github.com/wshobson/agents before installing.
Is block-no-verify-hook free to use?
Yes. block-no-verify-hook is free and open source under the MIT license, so you can read, run, and adapt it within that license's terms.
Which agents does block-no-verify-hook work with?
block-no-verify-hook declares compatibility with Claude Code. Agent Skills use a portable SKILL.md format, so other compatible clients can usually load it too.
Where does block-no-verify-hook come from?
block-no-verify-hook ships inside wshobson/agents, a repository that contains 53 catalogued skills in total. The repository's 38,529 GitHub stars apply to that whole collection, not to this skill on its own.

Related skills

More Workflow →

Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.

39k wshobson MIT

Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.

39k wshobson MIT

Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.

39k wshobson MIT

Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration. Use this skill when debugging bugs with multiple potential causes, performing root cause analysis, or organizing parallel investigation workflows.

39k wshobson MIT

Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system simultaneously, when establishing file ownership to prevent merge conflicts in a shared codebase, when designing interface contracts so parallel implementers can build against each other's APIs before they are ready, or when deciding whether to use vertical slices versus horizontal layers for a full-stack feature.

39k wshobson MIT