instruction-validate

To validate instruction frontmatter, run the validator on a target instruction path to verify conformance against a standard template. It checks for required fields and sections, outputting a validation report with actionable feedback to ensure consistent documentation quality.

Yes, you can use documentation lint checks during code reviews and pre-commit checks to enforce quality gates. The validator verifies links, references, and required sections, preventing drift between specs and implementation before changes are committed.

Instruction validation is the process of checking that an instruction file complies with standard frontmatter and required references. You need it during new instruction creation, updates, and pre-commit checks to enforce uniform structure and links across documentation.

Yes, the validator checks that all links and references exist and are well-formed. It performs structural checks against a defined template and outputs a validation report with actionable guidance to fix any missing or malformed references.

The best way to prevent drift is to validate instructions against standard frontmatter, required sections, and references. Running this validation during creation, updates, and code reviews enforces a uniform structure and ensures consistent quality across documentation.