dev-docs-review

To check for stale documentation, you can run an automated review sweep that identifies outdated references, invalid cross-links, and misaligned plans across your READMEs and project files.

Yes, you can automatically fix broken cross-links and correct misspellings by running the documentation review with an auto-fix flag to apply structured remediation directly to the affected files.

You can review documentation for a specific pull request by using targeted flags like --pr to focus the sweep on changes from that PR, ensuring references remain valid without scanning the entire project.

The best way to keep CLAUDE.md references and skill mappings aligned is to run a comprehensive documentation health check that verifies references against the actual filesystem and reports discrepancies.

Yes, the documentation review works for targeted lesson tracks by using specific flags like --lesson, allowing you to focus on a single track or lesson rather than sweeping all root docs and lesson trees.

You should use an automated documentation review when your repository contains extensive READMEs, plans, and cross-links that are difficult to track manually, ensuring all references remain valid and aligned.