Writing Hookify Rules

Hookify rules detect patterns in file edits and prompts by matching regex against bash, file, stop, and prompt events. Define a YAML frontmatter with name, enabled, event, and action fields, then specify a regex pattern and the message shown when triggered. Rules execute automatically during Claude Code interactions without manual review.

Hookify rules support bash, file, stop, and prompt events. Bash events catch dangerous commands like rm -rf. File events monitor edits to specific patterns. Prompt events intercept user inputs. Stop events halt execution when conditions match, providing layered workflow enforcement across all interaction types.

Yes, hookify rules support multi-condition patterns beyond single regex matches. Define conditions with field, operator, and pattern fields in YAML frontmatter to combine multiple checks. This enables complex enforcement logic—for example, detecting console.log only in production files or flagging missing deployment checklist entries.

Create a hookify rule with event set to bash and pattern set to your regex—such as rm\s+-rf for recursive deletes. Set action to warn or stop, then write a message shown when the pattern matches. Store the rule as a .claude/hookify.{rulename}.local.md file to activate it automatically.

Warn actions display a message when a rule triggers but allow execution to continue, useful for code style guidance. Stop actions halt execution and block the operation, appropriate for security violations or process enforcement. Choose based on whether the pattern is advisory or mandatory.

No, hookify rules use declarative YAML frontmatter and markdown, requiring no custom code. Write the rule definition directly in a .claude/hookify.{name}.local.md file in your workspace. Rules activate automatically without build steps or configuration beyond the markdown file.