FREE HOOK COVERAGE CHECKER

Claude Code hooks checker: find rules with no enforcement

Paste your settings.json hooks array and your CLAUDE.md text. This audit flags every "never", "always", or "must" rule that has no matching hook behind it, and suggests the hook JSON to close the gap.

This free Claude Code hooks checker audits whether a project's CLAUDE.md rules are actually enforced by its settings.json hooks, or just advisory text the model can ignore under pressure. It scans CLAUDE.md for imperative rules ("never commit secrets", "always run tests", "never force-push"), cross-checks each against the hook events configured in settings.json, and scores the percentage of rules backed by a deterministic hook. Everything runs in your browser, with no signup and no upload.

Loading tool…

FAQ

Why does a CLAUDE.md rule need a hook at all?

CLAUDE.md rules are advisory: the model reads them and tries to follow them, but under a long session, a tricky task, or competing instructions, it can drift and skip one. A hook in settings.json runs a real shell command on a matching event (PreToolUse, PostToolUse, Stop, etc.) and can block or flag the action outright, so the rule is enforced regardless of what the model decides to do.

How does the checker decide a rule is "enforced"?

It matches imperative phrasing in CLAUDE.md ("never", "always", "must", "don't") against a set of common rule categories — formatting, running tests before finishing, blocking secret commits, blocking force-pushes, blocking `any` types — and checks whether settings.json has a hook registered for the event that category would need (for example PostToolUse for formatting, PreToolUse for blocking a git command). It's a heuristic match on rule category and hook event, not a guarantee the hook's exact command does the right thing.

What if my settings.json has hooks but my CLAUDE.md doesn't mention the matching rule?

That's fine and common — a hook doesn't need a CLAUDE.md rule to work. This checker only flags the other direction: a CLAUDE.md rule with no hook behind it, which is the gap worth closing since the model has no deterministic backstop for that rule.

How is this different from the Hooks JSON Builder?

The Hooks JSON Builder authors a brand-new hook from scratch when you already know you want one. This checker starts from your existing CLAUDE.md and settings.json and tells you which rules you've already written down have no hook at all, so you know what to build next.

How is this different from the CLAUDE.md Linter?

The CLAUDE.md Linter scores CLAUDE.md in isolation for vagueness and bloat. This checker takes a step further: it only cares about rules phrased as hard constraints, and checks them against your actual settings.json hooks to see which ones are backed by real enforcement versus just advisory text.

Is anything uploaded?

No. Parsing and the coverage check run entirely in your browser. Nothing is uploaded or stored, and no signup is required.

By Rakshit Yadav · Published 2026-10-31 · Last updated 2026-10-31. Next: generate the missing hook from plain English, build a new hook for an unenforced rule, or lint your CLAUDE.md for bloat and vagueness.

[ RUNS IN YOUR BROWSER • DROP A FILE OR TAP GENERATE • NO SIGNUP ]

Go further

Liked the free tool? Get the kits.

Engineering, Marketing, or Both: agents, skills, and slash commands you drop into any Cursor project.