skill-check-rule

To audit skill documents for consistency, scan the repository to enforce frontmatter keys, verify cross-document references, and check governance alignment. This process detects mismatches across documents, frontmatter, and implementation notes.

Mismatches between frontmatter and implementation notes occur when skill documents drift from their original governance rules. Auditing the interlinked document set detects naming inconsistencies, invalid paths, and missing history to ensure compliance.

Validating cross-document references in a skill repository is best handled by running an automated audit that cross-checks governance assignments and interlinked rules. This identifies invalid paths and ensures references remain correct across the documentation.

Yes, you can enforce naming consistency across interlinked governance documents by applying an audit rule set to the repository. This verifies that frontmatter keys and document IDs align correctly, identifying missing history or invalid paths.

Generating remediation guidance for documentation discrepancies requires auditing the document set to detect mismatches. Once discrepancies are found in frontmatter or references, the audit produces actionable guidance to correct the drift.