Compare code changes against READMEs to detect documentation drift.
npx skills add https://github.com/TrevorPLam/agency --skill scan-docs-drift
Please help me install this Agent Skill. Skill: scan-docs-drift Source: https://github.com/TrevorPLam/agency/tree/main/.windsurf/skills/scan-docs-drift Command: npx skills add https://github.com/TrevorPLam/agency --skill scan-docs-drift
Detects stale or drifted documentation by comparing recent code changes to corresponding READMEs, helping teams maintain alignment between implementation and documentation.
Run the drift scan after code or docs changes to surface mismatches between implemented code and documentation.
High-intent search queries and answers about installing and using this skill.
To detect documentation drift, you can scan your repository's git history to compare recent code changes against corresponding READMEs. This surfaces stale documentation mismatches across packages and apps, generating a structured drift report for issue tracking.
The best way to audit stale documentation before a release is to scan code changes and locate outdated docs across packages. Comparing implementation updates against READMEs ensures alignment and generates actionable issues for documentation reviews.
You can generate a drift report by running a scan that requires access to git history within your repository. It operates on docs and code references to identify mismatches, outputting a structured report of outdated documentation for ongoing maintenance.
Yes, documentation drift detection works across multiple packages and apps. It identifies code changes and locates outdated docs throughout your project structure, ensuring alignment between implementation and documentation updates during software reviews.
You need to scan for documentation drift during software documentation reviews, release planning, and ongoing maintenance. Running the scan after code or docs changes surfaces mismatches between implemented code and documentation to prevent stale references.
Your README no longer matches recent code changes due to documentation drift. By comparing git history against your docs, you can identify exactly where implementation updates occurred without corresponding documentation updates across your packages.
refactory-langGenerate baseline-spec.md and current-state.md from codebase and git history.
lev-osAudit codebase alignment against north star documentation and classify drift types.
tamziAudit top-level documentation against recent git history and open pull requests.
linenoizeGenerate and maintain project documentation from code and git history.
