writing-hookify-rules

Writing a Hookify rule requires creating a markdown file with YAML frontmatter specifying the name, enabled status, event type, and regex pattern to match the target bash command, followed by a message body containing structured safety guidance.

Required YAML frontmatter for Hookify rules includes name and description fields for discovery, alongside enabled, event, and pattern fields that define the trigger conditions and regex matching behavior for tool activity.

Hookify supports multi-condition rules by utilizing event-specific fields and match operators including regex_match, contains, equals, not_contains, starts_with, and ends_with to combine multiple matching criteria within a single rule definition.

Testing and refining Hookify rules involves using local .claude/hookify.{rule-name}.local.md files to safely validate regex patterns, verify syntax correctness, and check for false positives before activating rules globally.

False positives in Hookify rules typically stem from overly broad regex patterns that inadvertently match safe tool activity; refining regex syntax to target specific bash command structures prevents matching unintended actions.