Writing Hookify Rules

anthropics/claude-plugins-officialOfficial

This lets you set up guardrails for Claude Code by writing markdown files with YAML frontmatter that pattern match against bash commands, file edits, agent stops, or prompts. You drop these files in `.claude/hookify.{rule-name}.local.md` and define regex patterns that either warn or block when they match. The use cases are obvious: stop yourself from running `rm -rf /`, catch leftover `console.log` statements before commit, protect `.env` files, or require a checklist before the agent stops. It's straightforward regex matching with simple operators like `contains` and `starts_with`, nothing fancy. Worth setting up a few rules early so you don't have to babysit the agent as much later.

skills.sh installs: 7.4K
GitHub stars: 46.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add anthropics/claude-plugins-official --skill writing-hookify-rules --agent claude-code

Installs into .claude/skills of the current project.

Files

Writing Hookify Rules

Overview

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.