docs-review

To detect stale documentation in a GitHub pull request, you can automate PR documentation staleness detection. The skill analyzes code changes using regex patterns to match changed identifiers against in-repo documentation and flags outdated files.

Automated documentation review works by assessing code change impacts within a pull request. It searches repository documentation for drift, matches changed code identifiers against existing docs, and generates a list of flagged files with suggested severity.

Yes, you can run stale documentation detection without modifying files because the skill operates in read-only mode. It evaluates pull request code changes and generates findings of potentially outdated content for manual resolution without updating documentation.

The best way to flag outdated in-repo documentation during code review is to automate documentation search and analysis. This approach matches pull request code changes with repository documentation to flag potentially outdated content for review.

Stale documentation detection does not automatically update flagged files. It operates strictly in read-only mode to identify outdated content, providing a list of flagged files with a suggested severity to allow developers to perform manual resolution.