frontmatter-validation

Validates YAML frontmatter in Markdown documents against predefined templates and rules.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill frontmatter-validation-reeinharddd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontmatter-validation
Source: https://github.com/reeinharddd/impulsa-monorepo/tree/main/.github/skills/frontmatter-validation
Command: npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill frontmatter-validation-reeinharddd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guarantees that all documentation adheres to a strict YAML frontmatter standard, preventing inconsistencies and ensuring discoverability.

Core Features & Use Cases

  • Automated Validation: Checks for required fields, correct formats (dates, versions), and adherence to defined rules.
  • Template Enforcement: Ensures documents align with specific templates based on their type.
  • Use Case: When a new feature design document is saved, this Skill automatically verifies that it includes all mandatory fields like document_type, version, last_updated, and at least 5 keywords, flagging any errors before they are merged.

Quick Start

Use the frontmatter-validation skill to check the frontmatter of the file 'new-feature.md'.

Frequently Asked Questions about frontmatter-validation

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

FAQPage Schema
How do I validate YAML frontmatter in Markdown documents?

To validate YAML frontmatter in Markdown documents, use this Skill to check metadata against predefined templates and rules, enforcing required fields, date formats, and keyword presence for consistency.

How do I enforce required fields in Markdown metadata templates?

You can enforce required fields in Markdown metadata templates by defining rules for specific document types like feature designs or ADRs, ensuring mandatory fields such as document_type, version, and last_updated are present.

What's the best way to ensure documentation consistency across feature design files?

The best way to ensure documentation consistency is to automatically validate frontmatter against strict YAML standards before merging files, verifying that format correctness for dates and versions is met.

Can I check format correctness for dates and versions in frontmatter?

Yes, you can check format correctness for dates and versions in frontmatter by applying automated validation rules that verify metadata structure and format compliance against predefined templates.

Does frontmatter validation work with API specification documents?

Yes, frontmatter validation works with API specification documents, supporting various document types by enforcing adherence to defined rules and ensuring metadata discoverability and consistency.