enhance-hooks

To validate hook safety, you can automate reviews to discover, classify, and parse hook definitions. This process enforces checks like set -euo pipefail, validates frontmatter, and ensures correct exit codes and event types.

Checking Claude hooks for correct exit codes and event types requires parsing frontmatter and validating definitions against expected event schemas. Automated reviews can classify hook types and report mismatches to ensure correct execution flow.

Ensuring hook scripts use set -euo pipefail involves scanning script content for missing safety flags. Automated validation tools can detect the absence of these error handling mechanisms and generate reports or optional auto-fixes to align with best practices.

You can automatically fix frontmatter validation issues by running an automated safety review on your hooks directory. These reviews identify malformed frontmatter and can apply optional auto-fixes to align hook definitions with best practices.

Claude Code hooks often fail during workflow automation due to incorrect exit codes, missing set -euo pipefail safety flags, or invalid frontmatter event types. Validating hook definitions helps discover these misconfigurations and enforce proper error handling.

You need to provide the path to your hook definitions directory to start an automated safety review. The validation process uses this path to discover, classify, and parse all relevant hook scripts and frontmatter configurations.