From claudelint
Validates Claude Code hooks.json files for schema correctness, event types, hook types (command/prompt/agent), matcher patterns, and command script references. Useful when hooks fail to fire or need debugging.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claudelint:validate-hooks [flags][flags]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Runs `claudelint validate-hooks` to validate `.claude/hooks/hooks.json` files.
Runs claudelint validate-hooks to validate .claude/hooks/hooks.json files.
claudelint validate-hooks $ARGUMENTS
--path <path> - Custom path to hooks.json--verbose - Show detailed output--warnings-as-errors - Treat warnings as errorsclaudelint validate-hooks
claudelint validate-hooks --path /path/to/hooks.json
npx claudepluginhub pdugan20/claudelint --plugin claudelintValidates hooks configuration in .claude/settings.json and hook scripts against the official Claude Code spec. Use after editing hooks or when a hook fails to fire.
Scaffolds Claude Code hooks with templates, validation, and conflict analysis. Analyzes existing hooks, prevents conflicts, and generates boilerplate code automatically.
Guides development of event-driven hooks for Claude Code plugins using prompt-based and command-based configurations in hooks.json for events like PreToolUse, PostToolUse, Stop, and SessionStart to validate tools and automate workflows.