What is a Hookify rule?

A Hookify rule is a markdown file with YAML frontmatter that defines specific patterns for Claude Code to monitor, triggering custom messages or actions when those patterns are matched.

What event types are supported?

Hookify supports 'bash' for terminal commands, 'file' for text edits, 'stop' for session completion, and 'prompt' for user-submitted text.

Can Hookify prevent Claude from running specific commands?

Yes, by setting the action to 'block' in the frontmatter, you can prevent Claude from executing matched bash commands or continuing the session.

Do I need to write code to create new hooks?

No, Hookify rules are designed to be 'no-code.' You only need to write simple markdown and YAML, though basic knowledge of regular expressions is helpful for complex patterns.

Where should I save my Hookify rules?

Rules should be saved in the .claude/ directory of your project root using the naming format: .claude/hookify.{rule-name}.local.md.

Hookify Rule Writing

Name: Hookify Rule Writing
Author: astrosteveo

byastrosteveo

Developer Tools

Enables the creation of custom Claude Code hooks and guardrails using simple markdown files and YAML frontmatter.

About

This skill provides comprehensive guidance for configuring Hookify, a tool that allows developers to define custom behavioral rules and project-specific guardrails for Claude Code without writing complex scripts. By leveraging markdown files with YAML frontmatter, users can intercept terminal commands, file edits, and session completion events to provide real-time warnings, block dangerous operations, or enforce best practices. It is particularly useful for teams looking to automate code reviews, prevent accidental data loss, and ensure consistent project standards within an AI-assisted development workflow.

Key Features

Dynamic rule loading for immediate updates without restarting
Regex-powered pattern matching for bash commands and file changes
0 GitHub stars
Markdown-based rule configuration with YAML frontmatter
Multi-condition logic for complex field-specific filtering
Event-driven triggers for terminal, file, stop, and prompt actions

Use Cases

Flagging insecure or debug code patterns like console.log or eval during file edits
Preventing the execution of dangerous commands like rm -rf or unauthorized sudo usage
Creating mandatory completion checklists to verify tests and documentation before ending a session

About

Key Features

Dynamic rule loading for immediate updates without restarting
Regex-powered pattern matching for bash commands and file changes
0 GitHub stars
Markdown-based rule configuration with YAML frontmatter
Multi-condition logic for complex field-specific filtering
Event-driven triggers for terminal, file, stop, and prompt actions

Use Cases

Flagging insecure or debug code patterns like console.log or eval during file edits
Preventing the execution of dangerous commands like rm -rf or unauthorized sudo usage
Creating mandatory completion checklists to verify tests and documentation before ending a session