writing-hookify-rules

Hookify rules detect risky commands and file changes by using YAML frontmatter to define event triggers and regex patterns, paired with markdown messages that instruct Claude to warn or block the behavior automatically within the project directory.

A hookify rule file uses YAML frontmatter to define name, enabled status, event type, action, and pattern settings. This configuration allows Claude Code to watch for specific file changes, prompt patterns, or shell commands and respond with warn or block behaviors.

Yes, hookify supports advanced condition-based matching for file paths, content, and prompt text. You should use these advanced conditions when simple regex patterns cannot accurately capture the complex trigger logic needed for your specific Claude Code events.

You warn about .env file edits by creating a hookify rule that targets file edit events, uses a regex pattern matching the .env file path, and sets the action to warn with a clear markdown message explaining the risk so Claude can guide behavior automatically.

Hookify rules require placement in the project .claude directory for project-level activation. Proper file naming and organization within this directory ensure the Claude Code-compatible hook system correctly detects events and triggers the configured warn or block behaviors.

Regex patterns for prompt text detection may struggle with complex contextual matching. When simple regex syntax cannot accurately capture nuanced trigger conditions, hookify allows transitioning to advanced condition-based matching for file paths, content, and prompt text.