review-docs-drift

You can prevent documentation rot by automatically analyzing pull request diffs to identify code changes that invalidate technical claims, file paths, default values, or architectural descriptions in the repository documentation.

Automate compliance auditing by verifying repository documentation against strict canonical rules, checking for canonical home ownership and generated region integrity to ensure technical claims remain truthful after code modifications.

Yes, you need git access to check for documentation inconsistencies, as the analysis operates on pull request diffs and requires adherence to the repository's defined documentation structure and identifier-sources table.

When infrastructure code changes, the Skill identifies every document referencing outdated identifiers like service account names and flags them for updates, preventing user confusion and maintaining documentation accuracy across the repository.

Automated drift detection is not suitable when a repository lacks a defined documentation structure or identifier-sources table, as the validation logic depends on these canonical rules to map code changes to technical assertions.