Writing Hookify Rules

You create Hookify rules by defining declarative, frontmatter-driven markdown files in the .claude directory to govern pattern-based checks and messaging for code edits. This enforces policy-driven security guidelines and reduces risky changes.

Hookify rules are frontmatter-driven markdown files that define conditional patterns and actionable messages to validate events like bash, file, stop, and prompt. They provide a structured way to enforce policy-driven checks and reduce misconfigurations.

To write regex patterns for Hookify rule files, create a new markdown file at .claude/hookify.descriptive-name.local.md and define conditional regex patterns matching your target event. This applies to creating, editing, and validating rule definitions for your workflow.

Yes, Hookify supports creating and validating rule files for bash, file, stop, prompt, and all events. This allows you to enforce specific pattern-based checks and messaging across different stages of your Claude workflows.

The best way to structure frontmatter in local rule markdown files is to use a declarative format that satisfies the specific frontmatter requirements for Hookify. This structured approach ensures clear, actionable messages and proper validation for your defined rules.

Your Hookify rules may not be working if the markdown file does not satisfy the required frontmatter fields or if the regex patterns do not match the prompt event correctly. Properly validating and testing rule definitions ensures the checks trigger properly.