review-docs-claims

To check markdown documentation for factual inaccuracies, apply a review pass to touched docs and CLI surfaces that flags misrepresentations and verifies truthfulness against the current codebase. This surfaces factual issues in user-facing references.

RFC leakage in documentation occurs when internal RFCs or design decisions are referenced in user-facing docs without being captured in inventories. Detect it by reviewing markdown docs to highlight these unauthorized internal references.

Review prose quality and tone across markdown docs by applying a consistency check that flags grammar issues, tonal shifts, and stylistic inconsistencies. This ensures uniform prose quality throughout user-facing documentation.

Yes, you can audit CLI reference text for truthfulness by running a review pass on CLI surfaces that identifies inaccuracies and misrepresentations. This verifies that CLI references match the current codebase.

The best way to audit touched markdown docs for truth, tone, and RFC leakage is applying a unified review pass that checks for factual inaccuracies, flags prose quality issues, and highlights internal RFC references against the current codebase.