hookify-rules

Topics in the source

• Writing Hookify Rules
• Overview
• Rule File Format
• Basic Structure
• Frontmatter Fields
• Advanced Format (Multiple Conditions)
• Event Type Guide
• bash Events

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. | 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) | Condition fields by event: bash: command file: filepath, newtext, oldtext, content prompt: userprompt Operators: regexmatch, contains, equals, notcontains, startswith, endswith All conditions must match for rule to trigger. Match Bash command patterns: Dangerous commands: rm\s+-rf, dd\s+if=, mkfs Privilege escalation: sudo\s+, su\s+ Permissio

This is an excerpt. Refer to the complete source and its current requirements.