Writing Hookify Rules

Create and validate YAML frontmatter Hookify rules in .claude/hookify directories.

1|Updated Oct 14, 2025
One-click install
npx skills add https://github.com/Invictusprime7/unison-tasks-official --skill writing-hookify-rules-invictusprime7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Writing Hookify Rules
Source: https://github.com/Invictusprime7/unison-tasks-official/tree/main/claude-code-main/plugins/hookify/skills/writing-rules
Command: npx skills add https://github.com/Invictusprime7/unison-tasks-official --skill writing-hookify-rules-invictusprime7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hookify rule definition and management can be error-prone without a consistent pattern and frontmatter convention.

Core Features & Use Cases

  • Defines a clear YAML frontmatter schema for hookify rules (name, enabled, event, pattern, and optional conditions) and the required rule structure.
  • Provides guidance and examples for writing the message bodies shown when a rule triggers, plus guidance on conditions and events.
  • Use case: scaffold, audit, and validate hookify rules across .claude/hookify.*.local.md files to enforce safe and predictable behavior in Claude.

Quick Start

Create your first hookify rule in the repository and save it as .claude/hookify.{rule-name}.local.md with a descriptive name.

Frequently Asked Questions about Writing Hookify Rules

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

FAQPage Schema
How do I create YAML frontmatter rules for Hookify in Claude?

Hookify rules use YAML frontmatter in markdown files within the .claude/hookify directory, requiring fields like name, enabled, event, and pattern to automate and validate rule behavior safely.

What frontmatter fields are required for a valid Hookify rule?

A valid Hookify rule requires name, enabled, event, and pattern fields in its YAML frontmatter. Optional conditions fields can be added to further refine rule triggering logic.

How do I validate and test Hookify rules in markdown files?

Validate Hookify rules by checking markdown files in .claude/hookify directories for correct YAML frontmatter schema, ensuring required fields are present and message bodies follow safe structural conventions.

Can I add optional conditions to Hookify rule patterns?

Yes, optional conditions can be added to Hookify rule patterns alongside required frontmatter fields to provide additional guidance on when rules should trigger based on specific events.

What is the best way to structure Hookify rule message bodies?

Structure Hookify rule message bodies by following provided examples and guidance to ensure content displayed when rules trigger is clear, safe, and consistently formatted across all .claude/hookify markdown files.