hookify-rules

Name: hookify-rules
Availability: InStock
Author: khunglong-03

Create and manage hookify rules with YAML frontmatter and event patterns.

Updated Apr 6, 2026

Search Tags:#automation #markdown #patterns #regex #frontmatter #rules #hookify

Ready to run

npx skills add https://github.com/khunglong-03/Pathora_Version3 --skill hookify-rules-khunglong-03

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hookify-rules
Source: https://github.com/khunglong-03/Pathora_Version3/tree/main/.cursor/skills/hookify-rules
Command: npx skills add https://github.com/khunglong-03/Pathora_Version3 --skill hookify-rules-khunglong-03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines and enforces hookify rules to watch for specific patterns in code or text and provide guided responses when they match.

Core Features & Use Cases

YAML frontmatter-driven rule definitions stored as .claude/hookify.{rule-name}.local.md
Flexible trigger modes via event types (bash, file, prompt, all) and pattern matching
Clear messaging guidelines and examples to help users implement rules safely and effectively

Quick Start

Create a new hookify rule file with YAML frontmatter and a concise trigger message.

Frequently Asked Questions about hookify-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I define hookify rules using YAML frontmatter in Markdown?▼

To define hookify rules, create Markdown files with YAML frontmatter containing required fields: name, enabled, event, and pattern. Store these rule definitions in .claude/hookify.{rule-name}.local.md files to enable pattern matching and guided responses.

What event types are available for pattern matching in hookify rules?▼

Hookify rules support four flexible trigger modes via event types: bash, file, prompt, and all. These events determine when pattern matching activates, allowing you to watch for specific code or text patterns and provide guided responses.

Can I use optional conditions in hookify rule files?▼

Yes, hookify rules support optional conditions alongside the required fields: name, enabled, event, and pattern. Optional conditions allow you to refine pattern matching behavior and customize messaging guidelines for safer rule implementation.

What's the best way to structure a hookify rule file for automated enforcement?▼

Structure hookify rule files using YAML frontmatter with required fields (name, enabled, event, pattern) at the top, followed by a concise trigger message in the Markdown body. Place files in .claude/hookify.{rule-name}.local.md for proper pattern detection.

How do I test and update hookify rules in a Markdown-based rule system?▼

Test and update hookify rules by modifying the YAML frontmatter fields (name, enabled, event, pattern) in your .claude/hookify.{rule-name}.local.md files. Verify pattern matching triggers correctly and adjust messaging guidelines as needed for guided responses.

Why are my hookify rules not triggering on file pattern matches?▼

Hookify rules may not trigger if required frontmatter fields (name, enabled, event, pattern) are missing or incorrectly formatted. Ensure the event type is set to file, the enabled field is true, and the file is placed correctly in .claude/hookify.{rule-name}.local.md.