Skip to content
Development
Auto-invokedWhat is this?This plugin ships a FLOW.md router the engine fires, so the matching skill runs itself. No slash command to remember.Learn how →Skill

/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

Boost this skill
@pdugan20pdugan20@pdugan20
From plugin
claudelint
129 skills13 agents1 command1 hook
Install
$ npx -y skills add pdugan20/claudelint --skill validate-hooks --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/validate-hooks

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

SKILL.md

validate-hooks.SKILL.md
name: validate-hooks
description: 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.
version: 1.0.0
argument-hint: "[flags]"
allowed-tools:
  - Bash(claudelint:*)

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](../validate-all/SKILL.md) - Run all validators
Read it on GitHub ↗
Ships withclaudelint

A linter for Claude Code projects. Validates CLAUDE.md files, skills, settings, hooks, MCP servers, plugins, and more.

Get the whole plugin, auto-invoked
Stats
TypeScriptJavaScriptNodeBashGitHub
+3 tags
MarkdownAnthropicMCP
12
Stars
3
Forks
Active
Maintenance
TypeScript
Language
MIT
License
2d ago
Last commit
7mo ago
Created

Repo: pdugan20/claudelint

In this plugin
13 agents9 skills1 command1 hook
See everything inside

Other skills on claudelint.

See all 9 skills in claudelint