Where should I save my Hookify rules?

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

What kind of events can I trigger rules on?

You can trigger rules on bash commands, file edits (Edit/Write tools), the 'stop' event when a session ends, and user prompts.

Can Hookify prevent Claude from running specific commands?

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

Do I need to restart Claude to apply new rules?

No, Hookify rules are dynamic and are read from the file system on every tool use, meaning changes take effect immediately after saving the rule file.

What is Hookify in the context of Claude Code?

Hookify is a configuration system that allows users to define custom rules and patterns that Claude monitors during a session to provide warnings or block specific actions based on triggers.

Hookify Rule Identifier & Creator

Name: Hookify Rule Identifier & Creator
Author: Microck

byMicrock

•

Developer Tools

Configures automated guardrails and custom patterns for Claude Code to monitor bash commands, file edits, and project workflows.

About

This skill empowers developers to define custom behaviors and safety protocols for Claude Code using the Hookify system. By creating specialized rules with YAML frontmatter and regex patterns, users can trigger context-aware warnings or block dangerous operations across bash commands, file modifications, and session completions. It is particularly useful for teams looking to enforce project-specific coding standards, prevent security leaks such as hardcoded API keys, and automate complex deployment checklists directly within the Claude environment.

Key Features

Multi-event triggering including bash, file, stop, and prompt events
Advanced conditional matching using regex and field operators
81 GitHub stars
Automated warning messages and action blocking capabilities
Custom guardrail creation for Bash commands and file operations
Dynamic rule loading from local project-level markdown files

Use Cases

Automating code reviews by flagging debug code like console.log or eval
Preventing accidental execution of destructive commands like rm -rf
Enforcing pre-deployment checklists and project-specific verification steps

About

Key Features

Multi-event triggering including bash, file, stop, and prompt events
Advanced conditional matching using regex and field operators
81 GitHub stars
Automated warning messages and action blocking capabilities
Custom guardrail creation for Bash commands and file operations
Dynamic rule loading from local project-level markdown files

Use Cases

Automating code reviews by flagging debug code like console.log or eval
Preventing accidental execution of destructive commands like rm -rf
Enforcing pre-deployment checklists and project-specific verification steps