vf-doc-review

To audit technical documentation for accuracy and completeness, review API references, file paths, CLI commands, and cross-links, then validate the Getting Started guide end-to-end to ensure it works correctly. This process catches incorrect symbols and broken links.

A documentation review for technical writing quality checks frontmatter, headings, and code fences for correct structure, while ensuring the voice remains professional without AI-generated marketing prose. This maintains clear and reliable developer guides.

To verify that your Getting Started guide works correctly, validate the entire flow end-to-end to ensure it functions without missing steps. This completeness check confirms new users can successfully follow the setup instructions without errors.

Yes, this documentation review tool checks API references and CLI commands by auditing their symbols and paths for correctness. It ensures that all technical references in the documentation accurately reflect the actual system.

To check documentation structure for frontmatter and code fence issues, run an automated review that scans headings, cross-links, and formatting. This ensures your technical guides maintain proper hierarchical organization and valid syntax.