How do I test a new Hookify rule?

Hookify rules are dynamic; they take effect immediately on the next tool use (like a bash command or file edit) after you save the .local.md file.

Where should I store my custom rules?

Rules should be stored in your project's root under the .claude/ directory, following the naming convention hookify.{rule-name}.local.md.

What events can be monitored with Hookify?

Hookify supports multiple event types including 'bash' for terminal commands, 'file' for code edits, 'stop' for session completion, and 'prompt' for user inputs.

Can I block Claude from running specific commands?

Yes, by setting the action field to 'block' in the rule's frontmatter, you can prevent Claude from executing matched bash commands or file edits.

What is a Hookify rule in Claude Code?

A Hookify rule is a markdown file with YAML frontmatter stored in the .claude directory that defines patterns to monitor and actions to take when those patterns match AI actions.

Hookify Rule Architect

Name: Hookify Rule Architect
Author: ANcpLua

byANcpLua

•

Security & Testing

Standardize and enforce AI coding behaviors by creating custom guardrails and validation rules for Claude Code.

About

Hookify Rule Architect provides a specialized framework for defining and implementing safety guardrails within Claude Code. It empowers users to create opinionated rules that monitor and restrict specific AI behaviors, such as preventing the execution of dangerous bash commands, flagging debug code like console logs, or enforcing mandatory checklists before a session ends. By utilizing regex patterns and multi-condition YAML frontmatter, this skill ensures that AI-driven development remains secure, compliant with project standards, and protected against common pitfalls like credential leaks or destructive file operations.

Key Features

Custom session completion checklists to enforce testing and documentation workflows.
Support for advanced conditional logic including regex, substring checks, and prefix matching.
Seamless hot-reloading where rules take effect immediately upon saving local configuration files.
1 GitHub stars
Automated detection and blocking of dangerous bash commands and privilege escalation.
Granular file-level monitoring to prevent the inclusion of debug statements or sensitive data.

Use Cases

Creating mandatory pre-deployment checklists that trigger whenever Claude attempts to stop a task.
Enforcing production-ready code standards by automatically flagging 'console.log' or 'eval' usage.
Preventing accidental execution of destructive shell commands like 'rm -rf' during AI tasks.

About

Key Features

Custom session completion checklists to enforce testing and documentation workflows.
Support for advanced conditional logic including regex, substring checks, and prefix matching.
Seamless hot-reloading where rules take effect immediately upon saving local configuration files.
1 GitHub stars
Automated detection and blocking of dangerous bash commands and privilege escalation.
Granular file-level monitoring to prevent the inclusion of debug statements or sensitive data.

Use Cases

Creating mandatory pre-deployment checklists that trigger whenever Claude attempts to stop a task.
Enforcing production-ready code standards by automatically flagging 'console.log' or 'eval' usage.
Preventing accidental execution of destructive shell commands like 'rm -rf' during AI tasks.