Writing Hookify Rules

Create custom hookify rules with regex pattern matching to block destructive bash commands like rm -rf before execution. Rules support configurable warn and block actions across bash commands, file edits, and agent stop events to prevent accidental damage.

Yes, hookify rules enforce coding standards automatically by warning about patterns like console.log in production files. Multi-condition matching using regex, substring, and prefix/suffix validation catches non-compliant code before completion.

Regex pattern matching validates pre-completion steps by scanning bash commands, file edits, and user prompts against defined patterns. Simple regex handles basic checks while multi-condition rules combine regex, substring, and prefix/suffix matching for complex validation.

No, new hookify rules load dynamically without requiring environment restarts. This core feature lets development teams add or modify validation rules on the fly, maintaining continuous workflow protection.

Set up a hookify rule that enforces all .env file edits include a .gitignore check before saving. Configurable block actions prevent the save if validation fails.

Hookify rules monitor bash commands, file edits, agent stop events, and user prompts to cover all common development touchpoints. Multi-event support ensures security risk prevention across the entire development workflow.