writing-hookify-rules

Define custom Hookify automation rules using markdown with YAML frontmatter.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to creating custom rules for the Hookify tool, enabling users to automate code quality checks, enforce best practices, and prevent common errors.

Core Features & Use Cases

  • Rule Definition: Learn the YAML frontmatter structure for defining rule names, events, patterns, and messages.
  • Event Handling: Understand how to trigger rules based on bash, file, stop, or prompt events.
  • Pattern Matching: Master simple and advanced regex patterns for precise condition matching.
  • Use Case: You need to ensure that no sensitive API keys are accidentally committed to your codebase. You can create a Hookify rule that triggers a warning whenever a file containing API_KEY is modified.

Quick Start

Create a new hookify rule by defining its name, event, and pattern in a .local.md file within the .claude directory.

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 custom automation rules for code quality checks?

Create custom automation rules by defining rule names, events, patterns, and messages in a markdown file with YAML frontmatter to enforce best practices and prevent common errors.

How do I trigger an automation rule based on bash commands or file edits?

Trigger automation rules by configuring `bash`, `file`, `stop`, or `prompt` events in the YAML frontmatter to handle specific workflow actions and file modifications.

How does regex pattern matching work for code automation rules?

Regex pattern matching validates conditions precisely by testing simple and advanced patterns against event outputs, enabling proactive error prevention through dynamic rule configuration.

Can I use markdown to define conditional logic for developer tools?

Yes, you can define conditional logic for developer tools using a structured markdown format with YAML frontmatter to manage dynamic code automation and event handling.

What is the best way to prevent sensitive API keys from being committed to a codebase?

Prevent sensitive data leaks by creating a rule that triggers a warning whenever a file containing `API_KEY` is modified, using regex pattern matching to enforce the condition.