writing-rules

Hookify rules require structured frontmatter with name, enabled, event, and pattern fields to validate correctly in CI workflows. This skill provides standardized templates and guidance for creating rule files that integrate quickly into automated editor checks.

Hookify rule files need frontmatter fields including name, enabled, event, and pattern, with optional conditions. This skill defines these structural requirements and provides templates to ensure your rules satisfy validation checks across projects.

Testing hookify rules involves creating a sample rule file at the project root and validating its frontmatter and patterns. This skill demonstrates workflows and examples to refine rule accuracy, conditions, and messages before deploying to real projects.

Markdown files with proper frontmatter can define hookify rules by specifying event triggers and validation patterns. This skill helps standardize markdown rule templates and validates their structure for consistent automated behavior.

Enforcing consistent hookify rules across projects requires standardized frontmatter templates and pattern definitions. This skill provides structured templates, testing guidance, and example formats to ensure rules behave uniformly in CI and editor workflows.

Hookify rule validation fails when frontmatter is incomplete or patterns and conditions are incorrectly structured. This skill guides writing effective conditions and messages, ensuring rules meet required frontmatter fields for proper validation.