I’m sure like most people on this sub, I was getting Claude to write docs for me for complex portions of the codebase. Occasionally Claude would use those docs for future development too. They were accurate when written, but as more changes landed they slowly went stale, and it got worse once multiple engineers and agents were all updating the code. When we intentionally change code, we also update the unit tests or they fail. But nothing fails when the docs go stale. They just quietly drift until they’re wrong. And when an agent reads those stale docs back into context on its next run, it’s working off bad information about the codebase, which is the opposite of what you want. So I made a small tool to deal with it. I’ve been running it on a few of my own codebases and it’s worked quite well, even used it in the development of itself. So I figured I’d share it and see what people think. No API keys, no LLMs, it’s entirely local and fast (written in Rust). It uses the AST to detect diffs and flags when a human or agent needs to review the docs, so cosmetic stuff (renames, formatting, comments) stays quiet and only actual logic changes trip it. It’s free and open source, I’m not selling anything, just looking for feedback. Link if you want to take a look: https://surface.gradientdev.xyz/ submitted by /u/AverageGradientBoost
Originally posted by u/AverageGradientBoost on r/ClaudeCode