writing-hookify-rules

You can prevent risky bash commands and unsafe file edits by creating event-driven rules that detect dangerous operations and generate context-sensitive warnings or blocks before they execute.

Regex rules can target bash commands, file edits, prompt inputs, and stop events. You can use single regex patterns or multi-condition rules with fields like file_path, new_text, and command to trigger warnings or blocks.

To block rm -rf or warn about secrets, create a markdown rule file in the .claude directory named hookify.{name}.local.md with YAML frontmatter defining the event, regex pattern, enabled flag, and action set to warn or block.

Yes, you can enforce team policies and require checklists by creating stop event rules that block agent termination until specific conditions are met, standardizing safety checks across repository workflows.

Yes, the system supports advanced multi-condition rules alongside simple single regex patterns, allowing you to combine fields like file_path, new_text, and command for complex detection logic before warning or blocking operations.

Rules must be placed specifically in the .claude directory as hookify.{name}.local.md files with valid YAML frontmatter. Detection is limited to configured event types and pattern matches, requiring manual rule maintenance for new safety policies.