validate-rules

Validate rule frontmatter against backbone schemas and coordinate maps.

11|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/reporails/rules --skill validate-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-rules
Source: https://github.com/reporails/rules/tree/main/.claude/skills/validate-rules
Command: npx skills add https://github.com/reporails/rules --skill validate-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate rules against schema and contracts to ensure correctness and consistency across rule definitions.

Core Features & Use Cases

  • Validate frontmatter against backbone schemas
  • Cross-check rule.md with rule.yml IDs and coordinate-map entries
  • Detect mismatches and provide actionable remediation

Quick Start

Run /validate-rules to validate all rules against their schema and contract mappings.

Frequently Asked Questions about validate-rules

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

FAQPage Schema
How do I validate YAML frontmatter against a schema contract?

You can validate YAML frontmatter by running integrity checks across rule.md and rule.yml files, ensuring all frontmatter fields match the backbone schemas and contract definitions.

What is the best way to cross-check rule.yml IDs with a coordinate map?

The best way to cross-check rule.yml IDs is using automated validation that verifies ID formats, slug consistency, and cross-validates entries against the coordinate map and supersession rules.

How do I detect frontmatter mismatches in rule definitions?

Detect frontmatter mismatches by validating rules against schema and contract mappings, which identifies inconsistencies between rule.md, rule.yml, and coordinate map entries while providing actionable remediation.

Can I validate slug consistency across multiple rule files?

Yes, you can validate slug consistency by running integrity checks that cross-validate rule.md and rule.yml files, ensuring ID formats and slugs match the coordinate map and supersession rules.

Why does my rule validation fail when IDs do not match the coordinate map?

Rule validation fails because the process cross-validates rule.md and rule.yml entries against the coordinate map, detecting ID format mismatches and slug inconsistencies to enforce contract standards.