What is the 'stop' event used for?

The 'stop' event triggers when Claude thinks it has finished a task. It is perfect for displaying checklists to ensure the agent has run tests or updated documentation before finishing.

How do I create a new Hookify rule?

Create a file named .claude/hookify.{name}.local.md with frontmatter specifying the name, event type (like bash or file), and the regex pattern to match.

Do I need to restart Claude to apply new rules?

No, Hookify rules are read dynamically. Once you save the .local.md file in the .claude directory, the changes take effect on the very next tool execution.

What is a Hookify rule in Claude Code?

A Hookify rule is a markdown file with YAML frontmatter stored in the .claude directory that tells Claude to watch for specific patterns and show warnings or block actions when those patterns are matched.

Can Hookify rules prevent Claude from deleting files?

Yes, by setting the event to 'bash', the pattern to an 'rm' command, and the action to 'block', you can prevent Claude from executing destructive commands.

Hookify Rule Identifier

Name: Hookify Rule Identifier
Author: Activer007

byActiver007

Developer Tools

Guides the creation and configuration of Hookify rules to enforce project guardrails and prevent dangerous operations in Claude Code.

About

The Hookify Rule Identifier skill empowers users to build a robust governance layer within Claude Code by defining custom 'Hookify' rules. These rules act as real-time monitors that intercept bash commands, file edits, and session stops based on regex patterns or specific conditions. Whether you need to prevent accidental deletions, block debug statements from reaching production, or enforce a pre-completion checklist, this skill provides the syntax, patterns, and best practices needed to automate project safety and compliance.

Key Features

Advanced multi-condition logic with operators like contains and regex_match
0 GitHub stars
Event-driven triggers for bash, file, stop, and prompt actions
Dynamic rule enforcement via local .claude configuration files
Regex-based pattern matching for shell commands and code edits
Customizable markdown messaging for warnings and suggestions

Use Cases

Preventing the execution of destructive shell commands like rm -rf in production environments
Blocking the inclusion of console.log, debugger, or sensitive credentials in source code
Enforcing mandatory quality checklists that Claude must verify before ending a task

About

Key Features

Advanced multi-condition logic with operators like contains and regex_match
0 GitHub stars
Event-driven triggers for bash, file, stop, and prompt actions
Dynamic rule enforcement via local .claude configuration files
Regex-based pattern matching for shell commands and code edits
Customizable markdown messaging for warnings and suggestions

Use Cases

Preventing the execution of destructive shell commands like rm -rf in production environments
Blocking the inclusion of console.log, debugger, or sensitive credentials in source code
Enforcing mandatory quality checklists that Claude must verify before ending a task