Where should Hookify rule files be stored?

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

What event types can trigger a Hookify rule?

Rules can trigger on 'bash' (command line tools), 'file' (editing or writing files), 'stop' (when the agent attempts to finish), 'prompt' (user input), or 'all' events.

How do I test my Hookify regex patterns?

You can test patterns using Python's re module in the terminal or use online tools like regex101.com using the Python flavor.

Can I prevent Claude from running specific commands?

Yes, by setting the 'action' field to 'block' in the rule's YAML frontmatter, you can prevent specific bash operations or file edits from proceeding.

What are Hookify rules in Claude Code?

Hookify rules are project-specific markdown files that define regex patterns for Claude to monitor, triggering custom messages or blocking actions when those patterns are matched during a session.

Hookify Rule Assistant

Name: Hookify Rule Assistant
Author: Activer007

byActiver007

Developer Tools

Guides the creation and configuration of project-specific guardrails and automated warnings using Hookify rule syntax.

About

The Hookify Rule Assistant skill empowers developers to implement custom project governance directly within Claude Code. It provides comprehensive guidance for writing Hookify rules—specialized markdown files that monitor environment events like bash commands, file edits, and session completion. By utilizing regex patterns and YAML frontmatter, this skill helps users automate the detection of dangerous commands, enforce coding standards, and create mandatory checklists, ensuring that Claude adheres to project-specific best practices and safety requirements.

Key Features

Support for various event types including bash, file, stop, and prompt
Expert guidance on YAML frontmatter configuration for Hookify rules
0 GitHub stars
Regex pattern optimization for bash commands and file content detection
Templates for common guardrails like blocking dangerous commands or flagging debug logs
Multi-condition logic support for complex workflow triggers

Use Cases

Preventing accidental execution of destructive shell commands like 'rm -rf'
Creating automated completion checklists that trigger before Claude finishes a task
Enforcing security standards by flagging the use of eval() or hardcoded API keys

About

Key Features

Support for various event types including bash, file, stop, and prompt
Expert guidance on YAML frontmatter configuration for Hookify rules
0 GitHub stars
Regex pattern optimization for bash commands and file content detection
Templates for common guardrails like blocking dangerous commands or flagging debug logs
Multi-condition logic support for complex workflow triggers

Use Cases

Preventing accidental execution of destructive shell commands like 'rm -rf'
Creating automated completion checklists that trigger before Claude finishes a task
Enforcing security standards by flagging the use of eval() or hardcoded API keys