Writing Hookify Rules

Define a Hookify rule with event type `bash`, use regex patterns to match commands like `rm -rf`, and set the action to `block` with a warning message. The rule triggers when Claude attempts the matched command and prevents execution while displaying your custom alert.

Yes, create a `file` event rule with pattern matching to detect specific file modifications. For example, match file paths and content patterns to warn Claude before adding debug statements like `console.log` to production files.

Warn actions display an alert to Claude but allow the operation to proceed; block actions prevent the operation and show your message. Use warn for guidance and block for hard guardrails on risky or policy-violating actions.

Hookify supports advanced rule formats with multi-condition logic in addition to simple regex patterns. Combine conditions using your rule definition to trigger only when multiple criteria match, enabling precise control over when rules apply.

Yes, Hookify supports `prompt`, `stop`, and `all` event types alongside `bash` and `file` events. This lets you enforce rules across the full interaction lifecycle, from user input through Claude's responses and operations.

Rules use YAML frontmatter for metadata fields like name, enabled, event, pattern, conditions, and action, followed by a markdown message body. This structured format makes rules both machine-readable and human-friendly for configuration.