Hooks
Event-driven scripts that run automatically at points in the Claude Code lifecycle.
What are you trying to do?
SessionEnd
SessionEndobservesUserPromptSubmit
UserPromptSubmitobservesPreToolUse (Bash)
PreToolUsecan blockPostToolUse (apply_patch|Edit|Write)
PostToolUsePostToolUse (mcp__aurora-dsql.*__transact)
PostToolUseSessionStart
SessionStartobservesTaskCreated
TaskCreatedobservesPostToolUse (Write|Edit)
Bitwize Music plugin hooks for quality enforcement
PostToolUsecan blockStop
Security guidance plugin — pattern-based warnings on edits, git-diff-based LLM review on stop
Stopcan blockSessionStart
SessionStartobservesElicitationResult
ElicitationResultobservesPostToolUse (Edit|MultiEdit|Write)
PostToolUsecan blockPostToolUseFailure
PostToolUseFailureobservesSessionEnd
SessionEndobservesPreToolUse (Write|Edit|Bash)
PreToolUsecan blockPreToolUse (Skill)
PreToolUsecan blockBeforeTool (run_shell_command)
BeforeToolcan blockPostToolUse (Bash)
Security guidance plugin — pattern-based warnings on edits, git-diff-based LLM review on stop
PostToolUsecan blockPostToolUse (Bash)
Security guidance plugin — pattern-based warnings on edits, git-diff-based LLM review on stop
PostToolUsecan blockSessionStart
SessionStart nudge directing the agent to delegate data-engineering tasks to altimate-code via the altimate-code skill. The UserPromptSubmit pre-run hook was removed because it double-invoked altimate-code (once at hook time, once when the model fired the skill), doubling token consumption on the al
SessionStartobservesPostToolUse (mcp__.*__find_columns|mcp__.*__get_dataset_columns|mcp__.*__get_dataset)
Pre-query column validation via schema caching. Catches unknown column errors before they hit the API by building a per-session schema cache from find_columns / get_dataset_columns / get_dataset results.
PostToolUseobservesUserPromptSubmit
UserPromptSubmitobservesPostToolUse
Hookify plugin - User-configurable hooks from .local.md files
PostToolUseobservesSessionStart
SessionStartobserves