Hookify Rules

This teaches Claude how to write Hookify rules, those markdown files with YAML frontmatter that watch for patterns in your commands and file edits. You'd use it when setting up project guardrails like blocking chmod 777, warning about console.log statements, or catching API keys in .env files. The skill covers the full syntax including event types (bash, file, stop, prompt), regex patterns, and the conditions format for complex rules. Worth noting it includes practical regex tips and common pitfalls, which matters since a pattern that's too broad will fire constantly and one that's too specific won't catch anything. The /hookify command can auto-generate rules from your conversation context, which is clever.

skills.sh installs: 3.5K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill hookify-rules --agent claude-code

Installs into .claude/skills of the current project.

Files

Writing Hookify Rules

Overview

ECC evaluates project-local Hookify rules with its built-in Node runtime. No separate Hookify plugin or Python installation is required when ECC hooks are enabled.

Hookify rules are markdown files with YAML frontmatter that define patterns to watch for and messages to show when those patterns match. Rules are stored in .claude/hookify.{rule-name}.local.md files.

Rule File Format

Basic Structure

---
name: rule-identifier
enabled: true
event: bash|file|stop|prompt|all
pattern: regex-pattern-here
---

Message to show Claude when this rule triggers.
Can include markdown formatting, warnings, suggestions, etc.