Which event types can trigger a rule?

Rules can be triggered by five event types: 'bash' for command-line tools, 'file' for edits and writes, 'stop' for session completion, 'prompt' for user input, or 'all' for every event.

Can I block Claude from performing an action?

Yes, by setting the 'action' field to 'block' in the rule's frontmatter, you can prevent the operation (like a dangerous bash command) from executing.

Where should Hookify rule files be stored?

Rules must be stored in the `.claude/` directory of your project root using the naming convention `.claude/hookify.{rule-name}.local.md`.

What are Hookify rules in Claude Code?

Hookify rules are markdown files with YAML frontmatter that define patterns Claude should monitor and specific messages it should display when those patterns are matched during tasks.

How do I test a new regex pattern for a rule?

You can test patterns using a simple Python command: `python3 -c "import re; print(re.search(r'your_pattern', 'test text'))"` or by using online regex testers with Python flavor support.

Hookify Rule Architect

Name: Hookify Rule Architect
Author: akiojin

byakiojin

•

Developer Tools

Simplifies the creation of automated safety checks and workflow enforcement rules for Claude Code environments.

About

The Hookify Rule Architect skill provides comprehensive guidance for authoring and managing Hookify rules—specialized Markdown files that monitor and govern Claude's behavior during development. By leveraging regex patterns and YAML frontmatter, this skill enables users to configure Claude to detect dangerous bash commands, prevent the commit of debug logs, and enforce project-specific best practices. Whether you need to block sensitive file edits or create completion checklists, this skill ensures your AI-driven development remains safe, consistent, and aligned with your team's standards.

Key Features

Advanced multi-condition logic for granular control over project-specific rules.
Real-time file monitoring to prevent shipping debug code or sensitive credentials.
Automated detection of dangerous bash commands like 'rm -rf' or privilege escalation.
Customizable event triggers for tool usage, session completion, and user prompts.
2 GitHub stars
Dynamic rule loading for immediate testing and iteration without environment restarts.

Use Cases

Enforcing pre-deployment checklists when Claude attempts to conclude a task.
Warning developers when sensitive configuration files or environment variables are modified.
Preventing the accidental inclusion of 'console.log' or API keys in production-bound code.

About

Key Features

Advanced multi-condition logic for granular control over project-specific rules.
Real-time file monitoring to prevent shipping debug code or sensitive credentials.
Automated detection of dangerous bash commands like 'rm -rf' or privilege escalation.
Customizable event triggers for tool usage, session completion, and user prompts.
2 GitHub stars
Dynamic rule loading for immediate testing and iteration without environment restarts.

Use Cases

Enforcing pre-deployment checklists when Claude attempts to conclude a task.
Warning developers when sensitive configuration files or environment variables are modified.
Preventing the accidental inclusion of 'console.log' or API keys in production-bound code.