create-hook

Event hooks are automation triggers that run code at specific points in a plugin's lifecycle—before or after tool use, during permission requests, or on notifications. Use the create-hook Skill to add a hook by specifying the event type (PreToolUse, PostToolUse, PermissionRequest, UserPromptSubmit, Notification, Stop, or SubagentStop), matching pattern, and command. The Skill reads or initializes hooks.json, appends your hook to the correct event array, and writes the file back.

Yes. Create a PostToolUse hook targeting the Write or Edit tools with a command like 'prettier --write $FILE'. The create-hook Skill handles the pattern matching and JSON configuration, so the hook executes your formatting command every time those tools complete.

Hook event types define when automation triggers: PreToolUse runs before a tool executes, PostToolUse runs after, PermissionRequest fires during permission checks, UserPromptSubmit on prompt submission, Notification on alerts, and Stop/SubagentStop on agent halting. Choose the type based on when you need your command to run in the tool workflow.

No. The create-hook Skill removes manual JSON editing by managing the hooks.json file directly. It reads the existing structure, appends your new hook to the appropriate event array, and writes it back, so you add multiple hooks through repeated Skill invocations without touching the file.

Hooks use pattern matching to target specific tools or apply globally. Configure the matching pattern when creating a hook—use a tool name like 'Write' or 'Edit' for selective triggering, or set a pattern that applies to all tools, depending on your automation use case.

The create-hook Skill initializes a new hooks.json file if it's missing, then appends your hook to the correct event array. You don't need to create the file manually; the Skill handles setup and writes a valid plugin hook configuration.