hookify-rules

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. Condition fields by event: Operators: regex_match , contains , equals , not_contains , starts_with , ends_with All conditions must match for rule to trigger. Match Bash command patterns: Match Edit/Write/MultiEdit operations: Completion checks and reminders. Pattern .* matches always. Match user prompt content for workflow enforcement. Minimum viable rule: - bash: command - file: file_path , new_text , old_text , content - prompt: user_prompt - Dangerous commands: rm\s+-rf , dd\s+if= , mkfs - Privilege escalation: sudo\s+ , su\s+ - Permission issues: chmod\s+777 - Debug code: console\.log\( , debugger - Security risks: eval\( , innerHTML\s*= - Sensitive files: \.env$ , credentials , \.pem$ - Escape special chars: . to \. , ( to \( - \s whitespace, \d digit, \w word char - + one or more, * zero or more, ? optional - | OR operator - 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 - Location : .claude/ directory in project root - Naming : .claude/hookify.{descriptive-name}.local.md - Gitignore : Add .claude/*.local.md to .gitignore - /hookify [description] -...