writing-hookify-rules

To write a custom Hookify rule, you define YAML frontmatter specifying the `bash` event type and use regex patterns to match dangerous commands. The rule body then defines the blocking action or warning trigger.

Hookify rules support configuration for `bash`, `file`, `stop`, and `prompt` event types. You select the appropriate event type in the YAML frontmatter to trigger rules based on code or command execution monitoring.

Yes, Hookify rules support both simple and advanced regex pattern matching for precise condition validation. This allows you to define specific triggers like detecting `API_KEY=` patterns before a commit action executes.

Yes, understanding YAML is required because custom Hookify rules rely on YAML frontmatter to define the rule structure, event types, and pattern matching logic. Knowledge of regex and Hookify's event-driven architecture is also necessary.

The Hookify event-driven architecture triggers custom rules when specified events occur. For file monitoring, you configure the `file` event type in your YAML frontmatter to execute defined actions when file patterns match your regex conditions.

The best way to prevent committing sensitive API keys is to create a Hookify rule using the `file` or `bash` event type with a regex pattern matching `API_KEY=`. The rule will trigger a warning or block the commit action when the pattern is detected.