hook-patterns

To validate bash commands with a PreToolUse hook, refer to the hook-patterns standards for file structure, script templates, and blocking response formats. These ensure automated pre-tool use actions execute consistently and securely before the command proceeds.

Claude Code hooks and skills differ in their trigger mechanisms and purposes. Hooks execute automated pre-tool use actions for validation and logging, whereas skills are broader functional modules invoked under different contextual conditions.

To validate commit messages before they are committed, implement a PreToolUse hook using the provided script templates and writing standards. This automates the validation process by intercepting the commit action and returning a blocking response format if the message fails checks.

Use PreToolUse hooks for automation tasks requiring validation before an action executes, such as checking commit formats. Use PostToolUse hooks for logging or triggering actions immediately after a tool completes its operation, ensuring secure tool execution workflows.

Standardized Claude Code hooks require a specific file structure and script templates defined in the hook writing standards. The blocking response format ensures that validation failures properly halt the automated tool execution workflow securely and consistently.