Best fit
Catches docs that drifted from the code: functions, CLI flags, and env vars in your docs that are gone from source.
// documentation
Doc Drift Detector
Catch documentation that drifted from your code: functions, CLI flags, and env vars named in your docs that are gone from the source.
What it flags
- Functions or methods in docs with no definition in source.
- CLI flags documented but missing from the parser.
- Env vars the docs mention but the code never reads.
- Example imports of missing modules.
- npm scripts or Make targets the docs reference but the project does not define.
How to run
Point it at your repo; it reads docs and source and cross-references them. Read-only.
Good to know
Heuristic; dynamic or meta definitions can cause false positives. Covers Python and JS/TS on the code side.
// choose with context
Is Doc Drift Detector the right skill?
It returns
Catches docs that drifted from the code: functions, CLI flags, and env vars in your docs that are gone from source.
Do not use it as
Do not treat a successful run as proof beyond the supplied files, declared scope, and evidence the skill actually checked.
Compatibility, access, version, and licence
- Reads or accesses
- Only the files or context you deliberately provide; review the listing before granting additional access.
- Compatibility
- Agents that read the open SKILL.md format. Verify runtime and service requirements at the purchase or install destination.
- Version
- Verify the current package version at the linked destination.
- Licence
- Review the package licence and seller terms at the linked destination.
Questions
What is the failure it prevents?
A reader following docs that reference code that no longer exists.
Does it change anything?
No. It is read-only and flags issues for you to act on.
Docs that match the code.
Current price and purchase option are shown on Agensi. Instant download. Works with any agent that reads SKILL.md.
Get Doc Drift Detector on Agensi