Doctective

Doctective analyzes pull requests to work out which documentation a code change affects. It builds semantic links between your source files and your docs, so when a function or flag changes, it knows which pages depend on it. You get a clear list of affected docs instead of guessing, and the review happens while the reasoning behind the change is still fresh in everyone's head.

Rather than just warning you, Doctective opens a second pull request with suggested documentation updates. The changes sit in your normal review flow, which means you can edit, reject, or merge them like any other diff, and the whole exchange stays inside the pull request where the original change already lives. It takes the blank-page problem out of doc maintenance, which is usually the real reason documentation work stalls in the first place.

The suggested edits come from an LLM that reads the code change and the surrounding documentation for context. It drafts new wording that matches what the code now does. Treat the output as a solid first draft, not a finished answer. You'll still want a human eye on anything user-facing.

Doctective handles TypeScript, JavaScript, Python, Java, Go, Rust, SQL, and more. On the documentation side it reads Markdown, MDX, JSDoc, and docstrings, so it works across most modern stacks without a format migration.

Setup runs through the Doctective GitHub App. You authorize it, choose the repositories to monitor, and it starts indexing. There's no CI pipeline to wire up by hand, which keeps adoption light for teams that don't want another config file.