rule-validate

To validate Claude Code rule files, run the validator on a specific rule name or the entire rules directory to check YAML frontmatter syntax, required fields, and path conventions. This ensures all rule definitions meet the required standards before merging.

Required YAML frontmatter fields for a rule file include name, description, and standard. The validation process checks for these mandatory fields and verifies correct YAML syntax to prevent formatting defects in the ruleset.

You can bulk check all rules by running the validator across the entire /.claude/rules directory. This all-rule scenario verifies trigger definitions, usage examples, and file naming conventions against the SSOT.

Yes, you can validate single-rule updates by providing the rule name without extension. The validator confirms path compliance, trigger accuracy, and frontmatter syntax, helping reviewers quickly identify non-compliant rules before merge.

Rule file trigger validation fails when trigger definitions and usage examples do not align with the SSOT. The validator enforces accurate trigger definitions to ensure rules activate correctly within the Claude Code environment.

The correct file path convention requires rule files to be located under /.claude/rules/ and follow specific naming conventions. The validator checks path compliance to ensure rules are discovered and applied correctly.