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 specific patterns to watch for and messages to show when those patterns match.

Where should I store my Hookify rule files?

All rules should be placed in the .claude/ directory of your project root and named following the pattern '.claude/hookify.{name}.local.md'.

Can I prevent Claude from executing a specific command?

Yes, by setting the 'action' field to 'block' in the rule's frontmatter, you can prevent operations that match your defined patterns.

Which events can I trigger rules on?

Rules can be triggered on 'bash' commands, 'file' edits (writing/modifying code), 'stop' events (when the agent finishes), and 'prompt' events (user input).

Do I need to restart Claude to apply new rules?

No, Hookify rules are read dynamically and changes take effect immediately on the next tool use or event trigger.

Hookify Rule Architect

Name: Hookify Rule Architect
Author: Xeonice

byXeonice

Developer Tools

Guides users in creating custom guardrails, safety warnings, and automated workflows for Claude Code using Hookify rule syntax.

About

The Writing Hookify Rules skill provides a comprehensive framework for defining custom behaviors and safety checks within the Claude Code environment. By utilizing markdown files with YAML frontmatter, users can configure Claude to monitor bash commands, file edits, and completion events. This skill offers precise guidance on writing regex patterns, setting up multi-condition logic, and crafting actionable messages that help prevent dangerous operations, enforce project-specific coding standards, and automate repetitive checklists.

Key Features

Best practices for actionable markdown message body creation
Comprehensive YAML frontmatter syntax guidance
Advanced multi-condition logic implementation
0 GitHub stars
Regex pattern optimization for bash and file events
Customizable warning and blocking action configurations

Use Cases

Enforcing project standards by flagging debug code like 'console.log' in production files
Preventing accidental execution of dangerous shell commands like 'rm -rf'
Implementing mandatory pre-completion checklists before an agent finishes a task

About

Key Features

Best practices for actionable markdown message body creation
Comprehensive YAML frontmatter syntax guidance
Advanced multi-condition logic implementation
0 GitHub stars
Regex pattern optimization for bash and file events
Customizable warning and blocking action configurations

Use Cases

Enforcing project standards by flagging debug code like 'console.log' in production files
Preventing accidental execution of dangerous shell commands like 'rm -rf'
Implementing mandatory pre-completion checklists before an agent finishes a task