review-docs-claims

To check documentation truthfulness before a release, you review user-facing Markdown files against the current implementation state to validate accuracy, prose quality, and identify any RFC leakage.

RFC leakage in technical documentation refers to references to Request for Comments documents that are not explicitly documented or intended for users. Analyzing Markdown files helps detect these unintended references.

You validate CLI reference text by running a documentation review workflow that compares user-facing Markdown prose against the actual implementation details to ensure accuracy and readability.

Yes, you can assess Markdown prose quality by running documentation verification workflows that analyze Markdown files to evaluate readability and ensure the text meets quality standards.

Yes, the documentation review process works with any Markdown directory, such as a 'docs-site' folder, by analyzing the contained files for truthfulness and prose quality without requiring external dependencies.

You should run a documentation integrity check when preparing for a release to ensure all user-facing documentation, CLI reference text, and examples accurately reflect the current state of the implementation.