Where should Hookify rules be stored?

Rules must be stored in the project's .claude/ directory using the naming convention .claude/hookify.{rule-name}.local.md.

Can Hookify rules prevent code from being written?

Yes, by setting the 'action' field to 'block' and targeting 'file' events, you can prevent Claude from writing specific code patterns or editing sensitive files.

What types of events can Hookify monitor?

Hookify can trigger on bash commands (bash), file modifications (file), session completions (stop), and user inputs (prompt).

Do I need to restart my session for rules to take effect?

No, Hookify rules are read dynamically and take effect on the very next tool use once the rule file is created or updated.

What is a Hookify rule in Claude Code?

A Hookify rule is a specialized markdown file with YAML frontmatter that tells Claude to watch for specific patterns and display messages or block actions when those patterns are detected.

Hookify Rule Architect

Name: Hookify Rule Architect
Author: Microck

byMicrock

•

111

Seguridad y Pruebas

Facilitates the creation and configuration of automated guardrails and workflow triggers within Claude Code using Hookify syntax.

Acerca de

The Hookify Rule Architect skill empowers users to define custom behaviors and safety checks for Claude Code by automating the creation of Hookify rule files. By leveraging YAML frontmatter and regex patterns, it allows for real-time monitoring of bash commands, file edits, and session completions, providing immediate warnings or blocking dangerous operations to maintain code quality and security standards across the development lifecycle.

Características Principales

Automated Hookify YAML frontmatter generation for various event types
Support for multi-condition rules including file paths and content checks
111 GitHub stars
Regex pattern matching for real-time command and code monitoring
Configurable 'warn' or 'block' actions for workflow enforcement
Standardized markdown message templates for developer guidance

Casos de Uso

Preventing the execution of dangerous terminal commands like 'rm -rf' or 'sudo'
Implementing custom 'stop' checklists to ensure tests and documentation are updated before finishing
Enforcing security standards by flagging 'console.log', 'eval', or hardcoded secrets

Acerca de

Características Principales

Automated Hookify YAML frontmatter generation for various event types
Support for multi-condition rules including file paths and content checks
111 GitHub stars
Regex pattern matching for real-time command and code monitoring
Configurable 'warn' or 'block' actions for workflow enforcement
Standardized markdown message templates for developer guidance

Casos de Uso

Preventing the execution of dangerous terminal commands like 'rm -rf' or 'sudo'
Implementing custom 'stop' checklists to ensure tests and documentation are updated before finishing
Enforcing security standards by flagging 'console.log', 'eval', or hardcoded secrets