Writing Hookify Rules

Automated detection rules for bash commands and file edits are written using YAML frontmatter with required fields like name, enabled, event, and pattern, followed by a clear message body to warn or block actions.

The YAML frontmatter schema for hookify rules requires four fields: name, enabled, event, and pattern. You can also include optional conditions to support multi-condition detection across typical development workflows.

Yes, you can enforce multiple conditions in a single hookify rule pattern. The schema supports both basic single-condition rules and advanced multi-condition rules to cover common security and quality checks.

To monitor and block specific actions, create a .claude/hookify.{descriptive-name}.local.md file containing a YAML frontmatter block with the required fields, followed by a clear message body for user guidance.

You can target bash command monitoring, file edits, prompts, and stop events when setting up workflow guardrails. This allows you to surface warnings or actions to keep development workflows safe.

Yes, hookify supports advanced security checks through multi-condition patterns. You can define rules with optional conditions to detect complex patterns in commands and text, providing structured and repeatable workflow guardrails.