Docs Review
Check all project documentation for staleness and fix what's drifted.
Process
- •
Scope the review:
- •Run
git log vLAST_TAG..HEAD --statto see what changed since last release - •Focus on docs affected by those changes
- •If no tag exists, review everything
- •Run
- •
Check each item:
File What to check src/lib.rsdoc commentLanguage count, feature list, API examples compile, Quick Start accuracy Cargo.tomldescription(crates.io one-liner),keywords,categoriesREADME.mdHardcoded versions (schema, install), feature list, usage examples, badge URLs CONTRIBUTING.mdArchitecture Overview matches current file layout — any files added/moved/renamed? SECURITY.mdThreat model current, dependency notes, any new attack surfaces? PRIVACY.mdData handling claims still accurate? CLAUDE.mdQuick Reference (version, schema, test count, language count) GitHub repo Description and topics — gh repo view, update withgh repo editif needed - •
Fix and report:
- •Fix stale docs directly
- •Report what was updated and what was already current
- •If unsure about a claim, flag it rather than guessing
When to run
- •Before releases (
/releasereferences this) - •After significant feature PRs
- •Before audits
- •When you suspect drift
Rules
- •Don't rewrite docs for style — only fix factual staleness
- •Don't add content — only correct what exists
- •Check numbers against code: grep for hardcoded counts (languages, tests, dimensions) and verify
- •If CONTRIBUTING.md Architecture Overview lists files, glob to confirm they exist