hookify-rules

You define regex rules using YAML frontmatter with fields like name, enabled, event, pattern, and message to watch for risky patterns in code and prompts. This creates automated guardrails that trigger warnings or blocks when patterns match.

Yes, hookify rules can monitor bash commands and file edits across software development pipelines. You specify the target event type in the frontmatter, and the rule triggers warnings or blocks when matching patterns are detected.

The best way to enforce security patterns is defining regex-based rules with cautionary messages in local markdown files. This approach automatically detects and responds to risky patterns, reducing unsafe actions without manual reviews.

To set up a new hookify rule, create a file at .claude/hookify.{rule-name}.local.md. Include the required YAML frontmatter fields like name, enabled, event, pattern, and a message to display when the rule triggers.

Yes, you can add advanced conditions to refine when a hookify rule triggers. These multiple optional conditions work alongside the required pattern field to precisely control when warnings or blocks activate during software development.

No dependencies are required to define hookify rules. You only need to create local markdown files with YAML frontmatter specifying the event, regex pattern, and message to start monitoring risky code and prompt patterns.