Writing Hookify Rules

Agent guardrails for file edits are written as Hookify rules using YAML frontmatter with event, pattern, and conditions fields to deterministically trigger warnings or blocks on specific bash, file-edit, or stop events.

A Hookify rule is a YAML configuration file with frontmatter that attaches deterministic trigger patterns and guidance messages to Claude, preventing unwanted agent actions during bash, file-edit, stop, and prompt events.

Regex matching in Hookify rules uses multi-condition fields targeting file_path, new_text, and command attributes, allowing you to specify precise pattern triggers for edited content and file paths within a single rule definition.

Hookify rule YAML frontmatter requires name, description, enabled, and event fields, plus correctly structured pattern or conditions blocks, so the rule loads dynamically from the expected local filename convention.

Yes, multi-condition Hookify rules target specific bash commands and file edits by combining fields such as command, file_path, and new_text to match complex agent behaviors and provide tailored Claude guidance messages.

Hookify rules fail to trigger when YAML frontmatter is malformed, regex patterns lack specificity, or the rule file is not stored in the expected local directory, preventing dynamic loading during file-edit events.