hookify-writing-rules

Hookify rules monitor specified patterns in prompts and code edits using YAML-frontmatter files. Create a rule in .claude/hookify.{rule-name}.local.md with frontmatter (name, enabled, event, pattern) and a message body. The rule triggers alerts when the pattern matches, letting you guide Claude behavior through warnings or blocks.

Hookify rules support bash, file, stop, prompt, and all events. Each event type triggers rules at different points: bash for shell commands, file for edits, prompt for input text, stop for execution halts, and all for any event. Match the event type to where you want pattern detection.

Yes, hookify rules support multi-condition patterns using a conditions block. Define multiple fields and operators in the advanced format to combine logic—for example, detecting both a specific keyword and file type together. The schema enforces frontmatter structure with name, enabled, event, optional action, and pattern fields.

Hookify rule messages should be clear and actionable, explaining what pattern triggered the alert and recommending next steps. Write the message body after frontmatter to guide users when a rule detects a match, ensuring the guidance is specific to the pattern and its context.

Single-condition patterns match one criterion directly in the pattern field, ideal for simple detections. Multi-condition patterns use a conditions block with multiple fields and operators, enabling complex logic like AND/OR combinations to catch nuanced scenarios across bash, file, stop, and prompt events.

Yes, hookify rules use YAML-frontmatter-based rule definition stored in .claude/hookify.{rule-name}.local.md files. The frontmatter declares the rule's metadata (name, enabled, event, action, pattern), and the message body provides user guidance when the rule triggers.