Writing Hookify Rules

Topics in the source

• Writing Hookify Rules
• Overview
• Rule File Format
• Basic Structure
• Frontmatter Fields
• Advanced Format (Multiple Conditions)
• Message Body
• Event Type Guide

Hookify rules are markdown files with YAML frontmatter that define patterns to watch for and messages to show when those patterns match. Rules are stored in .claude/hookify.{rule-name}.local.md files. name (required): Unique identifier for the rule Use kebab-case: warn-dangerous-rm, block-console-log Be descriptive and action-oriented Start with verb: warn, prevent, block, require, check enabled (required): Boolean to activate/deactivate true: Rule is active false: Rule is disabled (won't trigger) Can toggle without deleting rule event (required): Which hook event to trigger on bash: Bash tool commands file: Edit, Write, MultiEdit tools stop: When agent wants to stop prompt: When user submits a prompt all: All events action (optional): What to do when rule matches warn: Show message but allow operation (default) block: Prevent operation (PreToolUse) or stop session (Stop events) If omitted, defaults to warn pattern (simple format): Regex pattern to match Used for simple single-condition rules Matches against command (bash) or newtext (file) Python regex syntax Example: For complex rules with multiple conditions: Condition fields: field: Which field to check For bash: command For fi

This is an excerpt. Refer to the complete source and its current requirements.