writing-hookify-rules

Create Hookify rule files with YAML frontmatter and regex conditions.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/victorjoshi9/content--1- --skill writing-hookify-rules-victorjoshi9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-hookify-rules
Source: https://github.com/victorjoshi9/content--1-/tree/main/.claude/plugins/marketplaces/claude-plugins-official/plugins/hookify/skills/writing-rules
Command: npx skills add https://github.com/victorjoshi9/content--1- --skill writing-hookify-rules-victorjoshi9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you author Hookify rule files correctly so Claude can detect unwanted patterns, surface timely warnings, and enforce project-specific guardrails without handcrafting the syntax from scratch.

Core Features & Use Cases

  • Rule Authoring Guidance: Explains how to structure Hookify markdown files with the required frontmatter and message body.
  • Pattern and Condition Design: Covers simple regex rules and multi-condition checks for bash commands, file edits, stop events, and prompts.
  • Practical Rule Scenarios: Useful for blocking dangerous shell commands, warning on sensitive file edits, requiring completion checks, and creating reusable automation safeguards.

Quick Start

Ask the skill to help you create a Hookify rule for the behavior you want to detect and it will draft the correct markdown structure and pattern logic.

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 Hookify rules to block unwanted commands in Claude workflows?

You create Hookify rules by authoring markdown files with valid YAML frontmatter, regex or condition-based matching logic, and a clear message body to trigger warnings or blocks for specific repository guardrails.

What is a Hookify rule file and when do I need one?

A Hookify rule file is a markdown document with YAML frontmatter that detects unwanted command, file, prompt, and stop-event patterns in Claude workflows, used when you need configurable warnings, blocks, and completion checks.

Can I use regex matching to detect sensitive file edits in Hookify rules?

Yes, Hookify rules support simple regex matching and multi-condition checks for bash commands, file edits, stop events, and prompts to enforce project-specific guardrails.

How do I structure markdown files for Hookify rule authoring?

Hookify rule files require valid YAML frontmatter for configuration, regex or condition-based matching for pattern detection, and a markdown message body that defines the warning or block output for each trigger.

Does Hookify support multi-condition checks for completion checks and stop events?

Yes, Hookify supports multi-condition checks allowing you to configure warnings, blocks, and completion checks for repository-specific guardrails across bash commands, file edits, prompts, and stop events.

What are the limitations of regex-based Hookify rules for Claude workflows?

Hookify rules require valid YAML frontmatter and precise regex or condition-based matching logic; poorly structured markdown message bodies or invalid syntax will prevent the rule from triggering correctly.