Validate hooks
Validates Claude Code hooks.json files for schema, events, and commands. Use when user asks to "check my hooks", "validate hooks.json", "hook errors", "why isn't my hook firing", or "hook event types". Validates hook events, types (command, prompt, agent), matcher patterns, and command script references.From its SKILL.md
npx -y skills add pdugan20/claudelint --skill validate-hooksAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, as published. Nobody here has run it
Validate Hooks
Runs claudelint validate-hooks to validate .claude/hooks/hooks.json files.
Usage
claudelint validate-hooks $ARGUMENTS
Options
--path <path>- Custom path to hooks.json--verbose- Show detailed output--warnings-as-errors- Treat warnings as errors
What Gets Validated
- JSON syntax
- Hook events (tool-use, user-prompt-submit, etc.)
- Hook types (command, prompt, agent)
- Matcher validation (tool names, regex patterns)
- Command script file existence
Examples
claudelint validate-hooks
claudelint validate-hooks --path /path/to/hooks.json
See Also
- validate-all - Run all validators