docs-review

Review documentation changes by running automated checks against project style guides and verifying technical claims against the codebase. This process enforces frontmatter consistency, checks internal links, and triages editorial style versus technical accuracy.

Checking internal links and frontmatter involves enforcing frontmatter presence and consistency while validating link targets. A dedicated review process uses reference verification steps to ensure documentation updates meet project standards.

Verifying technical claims against the codebase requires applying a verification checklist during the documentation review. This triages technical accuracy by checking documentation updates against project references and actual codebase behavior.

Yes, documentation review works with Vale and available linters to surface style issues. If Vale or a linter is available, it runs against changed docs to automate style guide enforcement and identify editorial issues.

Run a documentation verification checklist when docs have been written or updated and need a quality check before submission. It is required for PR submissions in Tempo-related docs to ensure style, accuracy, and completeness.

Style triage identifies editorial issues aligned with style guides, while technical accuracy checks verify claims against the codebase. Documentation review distinguishes whether changes require editorial correction or deeper technical verification.