Detect documentation drift in Rust project files and repository metadata.
npx skills add https://github.com/jamie8johnson/cqs --skill docs-review-jamie8johnson
Please help me install this Agent Skill. Skill: docs-review Source: https://github.com/jamie8johnson/cqs/tree/main/.claude/skills/docs-review Command: npx skills add https://github.com/jamie8johnson/cqs --skill docs-review-jamie8johnson
Documentation often drifts from the codebase, making it harder to understand current behavior, setup, and policies. This skill identifies stale docs across key files (src/lib.rs doc comments, Cargo.toml description, README, CONTRIBUTING.md, SECURITY.md, PRIVACY.md) and the repo metadata, surfacing fixes to keep the project accurate and maintainable.
Run the docs-review skill to scan the repository and generate a drift report summarizing stale docs and suggested fixes.
High-intent search queries and answers about installing and using this skill.
Documentation drift in a Rust project is detected by comparing src/lib.rs doc comments, Cargo.toml descriptions, README, CONTRIBUTING, SECURITY, and PRIVACY files against the current codebase to generate a report with actionable fixes.
Keeping project docs current involves scanning repository metadata and core documentation files to identify stale content, then applying automated recommendations and suggested edits to restore alignment with recent code changes.
Yes, this documentation review process applies drift checks to GitHub repo metadata alongside core project files like README.md and Cargo.toml to ensure comprehensive accuracy and maintainability across the repository.
Fixing stale README and CONTRIBUTING files requires validating documentation against recent code structure changes, identifying misaligned content, and applying suggested edits to restore accuracy and prevent release drift.
Automating documentation maintenance for Rust libraries is possible by scanning src/lib.rs doc comments and Cargo.toml descriptions to validate consistency, then generating a precise drift report with suggested fixes.
A docs review checks src/lib.rs, Cargo.toml, README.md, CONTRIBUTING.md, SECURITY.md, PRIVACY.md, and repository metadata to identify documentation drift and surface fixes for keeping the project accurate.
N4M3ZEnforce Rust development conventions for the Forge ecosystem.
Camilo8902Generate documentation templates for README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT, LICENSE, and CHANGELOG files.
igor1309Detect factual mismatches between markdown documentation and code in a repository.
VictorHueniAudit repository documentation for staleness, broken references, and deprecated API usage.
