How do I trigger a rule based on a bash command?

Set the 'event' field in the rule's YAML frontmatter to 'bash' and provide a regex pattern to match the command you want to monitor.

What regex flavor does Hookify use?

Hookify uses Python's regex syntax for pattern matching across bash commands, file paths, and text content.

Where should Hookify rule files be located?

Rules should be saved in the project root under .claude/hookify.{rule-name}.local.md to be correctly identified and loaded.

What is a Hookify rule in Claude Code?

A Hookify rule is a specialized markdown file stored in the .claude/ directory that defines patterns to watch for and messages to display when those patterns are matched during a session.

Can I prevent Claude from performing an action using rules?

Yes, by setting the 'action' field to 'block', you can prevent the operation from proceeding when the rule's pattern or conditions are met.

Hookify Rule Identifier

Name: Hookify Rule Identifier
Author: Microck

byMicrock

•

Developer Tools

Provides comprehensive guidance and syntax templates for creating custom Hookify guardrails and project rules.

About

The Rule Identifier skill is designed to help developers implement automated guardrails and project-specific patterns within the Claude Code environment. By leveraging the Hookify rule format—a combination of YAML frontmatter and Markdown—this skill enables the configuration of triggers based on bash commands, file edits, and session events. It is particularly useful for teams looking to enforce coding standards, prevent dangerous command execution, and ensure completion checklists are followed through real-time, pattern-matched feedback.

Key Features

Standardized Hookify syntax for YAML frontmatter and Markdown body
Multi-condition logic using operators like contains, equals, and starts_with
Regex-based pattern matching for bash commands and file operations
89 GitHub stars
Action-oriented guardrails including warning and blocking modes
Event-driven triggers for bash, file, stop, and prompt actions

Use Cases

Enforcing code quality by flagging debug statements or sensitive data in specific file types
Preventing the use of dangerous commands such as 'rm -rf' or privilege escalation in the terminal
Creating mandatory pre-completion checklists to verify tests and documentation before the agent finishes

About

Key Features

Standardized Hookify syntax for YAML frontmatter and Markdown body
Multi-condition logic using operators like contains, equals, and starts_with
Regex-based pattern matching for bash commands and file operations
89 GitHub stars
Action-oriented guardrails including warning and blocking modes
Event-driven triggers for bash, file, stop, and prompt actions

Use Cases

Enforcing code quality by flagging debug statements or sensitive data in specific file types
Preventing the use of dangerous commands such as 'rm -rf' or privilege escalation in the terminal
Creating mandatory pre-completion checklists to verify tests and documentation before the agent finishes