I built Doctective after wasting one too many hours debugging issues caused by outdated docs.
Imagine this: Want to use a new library so you follow the documentation, it doesn't work, and then you discover the code changed 3 months ago but nobody updated the docs. The worst part? AI coding assistants are now reading these stale docs too, generating broken code based on outdated information.
So I built something simple: connect your GitHub repo, and Doctective watches every PR. When code changes would break your docs, it tells you and can even open a companion PR with the fixes automatically.
No new tools to learn. No manual doc audits. Just accurate docs that update themselves.
Would love your feedback — what's the #1 documentation pain point on your team?
starkparker•40m ago
This is dreadfully close in name to Doc Detective, an actively developed open-source tool launched several years ago with a very similar goal of associating tests with documentation contents to flag drift and automate corrections. https://doc-detective.com/, https://github.com/doc-detective/doc-detective
johnnymedhanie•1h ago
Imagine this: Want to use a new library so you follow the documentation, it doesn't work, and then you discover the code changed 3 months ago but nobody updated the docs. The worst part? AI coding assistants are now reading these stale docs too, generating broken code based on outdated information.
So I built something simple: connect your GitHub repo, and Doctective watches every PR. When code changes would break your docs, it tells you and can even open a companion PR with the fixes automatically.
No new tools to learn. No manual doc audits. Just accurate docs that update themselves.
Would love your feedback — what's the #1 documentation pain point on your team?