rule-validate

Validate Claude Code rule files for YAML frontmatter, format, and path compliance.

31|5|Updated Jan 14, 2026

Search Tags:#claude #validate #lint #code-review #frontmatter #rule

Ready to run

npx skills add https://github.com/NSEvteev/FullSpec --skill rule-validate-nsevteev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rule-validate
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/rule-validate
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill rule-validate-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill validates rule files to ensure they meet Claude Code standards, including required YAML frontmatter, proper formatting, correct file paths, and accurate trigger definitions.

Core Features & Use Cases

Frontmatter validation: checks for required fields (name, description, standard, etc.) and correct YAML syntax.
Path and format checks: ensures rule files are located under /.claude/rules/ and follow naming conventions.
Trigger and usage validation: verifies trigger definitions and usage examples align with SSOT.
Code review and audit readiness: helps reviewers quickly identify non-compliant rules before merge.

Use Case: A maintainer adds a new rule or updates an existing one; run /rule-validate to confirm validity and prevent defects from entering the standard ruleset.

Quick Start

Provide the rule name (without extension) and run the validator to verify compliance.

Frequently Asked Questions about rule-validate

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

FAQPage Schema

How do I validate Claude Code rule files for YAML frontmatter and format compliance?▼

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.

What are the required YAML frontmatter fields for a Claude Code rule file?▼

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.

How do I bulk check all rules under .claude/rules for trigger and path compliance?▼

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.

Can I use a rule validator to review single-rule updates before a merge?▼

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.

Why does my Claude Code rule file fail trigger definition validation?▼

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.

What is the correct file path convention for Claude Code rule files?▼

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.