$ loading_

$ ~/registry/skill/affaan-m-hookify-rules

SKILL

hookify-rules

Create, configure, and refine Hookify rules and syntax patterns.

Stars

★ 229,796

Source

GitHub

Updated

2026-07-15

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 229.8k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "hookify-rules" skill from askskill:
1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/skills/hookify-rules/SKILL.md
2. Save it as ~/.claude/skills/hookify-rules/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Write a New Hookify Rule

Prompt

Help me write a Hookify rule: when package.json is modified, automatically remind me to run a dependency check. Please provide a sample rule and explain each field.

Expected

A usable Hookify rule example with field explanations and usage notes.

Configure Matching Syntax

Prompt

I want to configure a Hookify rule that triggers only when files under src/**/*.ts change. Please provide the correct Hookify syntax and explain how the wildcard pattern matches.

Expected

A Hookify-compatible matching rule plus a clear explanation of path patterns and trigger conditions.

Debug a Rule Error

Prompt

Here is my Hookify rule. Please check why it is not working, identify syntax issues, and provide a corrected version:
[paste rule content here]

Expected

A diagnosis of the current rule, explanation of the error, and a corrected complete rule.

// docs

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.

Frontmatter Fields

Field	Required	Values	Description
name	Yes	kebab-case string	Unique identifier (verb-first: warn-, block-, require-*)
enabled	Yes	true/false	Toggle without deleting
event	Yes	bash/file/stop/prompt/all	Which hook event triggers this
action	No	warn/block	warn (default) shows message; block prevents operation
pattern	Yes*	regex string	Pattern to match (*or use conditions for complex rules)

Advanced Format (Multiple Conditions)

---
name: warn-env-api-keys
enabled: true
event: file
conditions:
  - field: file_path
    operator: regex_match
    pattern: \.env$
  - field: new_text
    operator: contains
    pattern: API_KEY
---

You're adding an API key to a .env file. Ensure this file is in .gitignore!

Condition fields by event:

bash: command
file: file_path, new_text, old_text, content
prompt: user_prompt

Operators: regex_match, contains, equals, not_contains, starts_with, ends_with

All conditions must match for rule to trigger.

Event Type Guide

bash Events

Match Bash command patterns:

Dangerous commands: rm\s+-rf, dd\s+if=, mkfs
Privilege escalation: sudo\s+, su\s+
Permission issues: chmod\s+777

file Events

Match Edit/Write/MultiEdit operations:

Debug code: console\.log\(, debugger
Security risks: eval\(, innerHTML\s*=
Sensitive files: \.env$, credentials, \.pem$

stop Events

Completion checks and reminders. Pattern .* matches always.

prompt Events

Match user prompt content for workflow enforcement.

Pattern Writing Tips

Regex Basics

Escape special chars: . to \., ( to \(
\s whitespace, \d digit, \w word char
+ one or more, * zero or more, ? optional
| OR operator

Common Pitfalls

Too broad: log matches "login", "dialog" — use console\.log\(
Too specific: rm -rf /tmp — use rm\s+-rf
YAML escaping: Use unquoted patterns; quoted strings need \\s

Testing

python3 -c "import re; print(re.search(r'your_pattern', 'test text'))"

File Organization

Location: .claude/ directory in project root
Naming: .claude/hookify.{descriptive-name}.local.md
Gitignore: Add .claude/*.local.md to .gitignore

Commands

/hookify [description] - Create new rules (auto-analyzes conversation if no args)
/hookify-list - View all rules in table format
/hookify-configure - Toggle rules on/off interactively
/hookify-help - Full documentation

Quick Reference

Minimum viable rule:

---
name: my-rule
enabled: true
event: bash
pattern: dangerous_command
---
Warning message here

// from the same source

deep-research

Conduct multi-source web research and produce cited, source-attributed reports.

seo

Audit, plan, and implement SEO improvements for better search visibility.

unified-notifications-ops

Unify multi-channel notifications for routing, deduplication, escalation, and inbox consolidation.

documentation-lookup

Fetches up-to-date framework docs for setup, APIs, and code examples.

iterative-retrieval

Refine retrieved context iteratively to improve subagent understanding and output quality.

dynamic-workflow-mode

Design adaptive agent workflows with eval gates and reusable skill extraction.

// similar tools

create-hook

Create hook JSON files for policy enforcement and agent lifecycle automation.

microsoftGet→

skillify

Turn a repeated workflow into a reusable skill file from the current session.

microsoftGet→

rules-distill

Extract shared principles from skills and turn them into maintainable rule files.

skill-comply

Generate test scenarios and measure how well agents follow skills and rules.

prompt-optimizer

Analyze and refine raw prompts into ready-to-use high-quality prompts.

skill-creator

Create or update skills that extend Codex with knowledge, workflows, and tools.