Developer Proposes Automated Documentation Drift Detection via Git History

On November 5, 2026, a developer published a post on DEV Community describing a practical way to detect documentation drift automatically from Git commit history. In the post, the author says that five days after publishing the docs for their app, 36 of its 37 pages described code that had changed since. Their code changes many times a day, mostly through AI coding agents; the commits passed their tests while the words drifted without anything going red. The post also notes that three sets of prose describe the same app: the public docs, the descriptions the in-app assistant reads to know what each screen does, and the tool descriptions that its MCP server gives to other programs. The proposed solution compares each file's modification time against the time it was last checked, so that code changes force the corresponding documentation to be updated. According to the author, this works without any LLM calls. The idea is presented at this stage as a personal write-up on DEV Community, and the material does not cover any implementation, tooling, or follow-up developments.