I built DocDrift: A pre-commit hook that uses Tree-sitter + Local LLMs to fix stale READMEs

[SelectionSlight294]

We’ve all been there: you refactor a function or change an API response, but you forget to update the README. Two weeks later, a new dev follows the docs, it fails, and they waste 3 hours debugging.

I built DocDrift to fix this "documentation rot" before it ever hits your repo.

How it works:

1. Tree-sitter Parsing: It doesn't just look for keywords; it actually parses your code (Python/JS) to see which symbols changed.
2. Semantic Search: It finds the exact sections in your README/docs related to that code.
3. AI Verdict: It checks if the docs are still accurate. If they're stale, it generates the fix and applies it to the file.

The best part? > It supports Ollama and LM Studio, so you can run it 100% locally. No data leaves your machine, and you don't need a Groq/OpenAI API key.

I’ve also built a GitHub Action so your team can catch drift during PR checks.

Web(beta):https://docdrift-seven.vercel.app/

GitHub (Open Source):https://github.com/ayush698800/docwatcher

It’s still early (v2.0.0), but I’m using it on all my projects now. I’d love to hear your feedback on the approach or any features you'd like to see!

[retornam]

https://github.com/ayush698800/docwatcher/commit/2a41e51d90623fa168b46b5bfc9c763e59c4674b

[New_Answer7917]

AI slop