Let me tell you how API docs die.
Nobody decides to let them rot. You ship a feature on Tuesday, promise yourself you'll update the docs on Wednesday, and by Friday something else is on fire. Six months later your docs describe an API that doesn't exist anymore.
The obvious fix is to let an LLM write them. So I tried that. It read my code and gave me something confident, polished, and partly made up. It documented an endpoint that wasn't there.
That was the moment the problem changed shape for me. The AI wasn't bad at writing. I had just given it two jobs: figure out what my API does, and explain it. The explaining, it's great at. The figuring out should never be a guess.
So I split the jobs
That's the whole idea behind Docloom. **The AI describes. It never discovers.
- A parser reads the code first.** Routes, function signatures, params and types come from a real AST parser, not regex and not vibes.
- Then the AI writes the words.** It only gets to describe what the parser already found, so it can't invent a route. It never gets the chance to go looking.
- everything gets checked.** Each claim in the generated text is compared against your source before anything is published.
Think of it as a writer who's only allowed to write about facts a fact-checker already signed off on.
You stay in control
When you regenerate after a merge, Docloom shows you a diff of what changed. Nothing goes live until you look at it and approve it. Docs you never reviewed are how this problem started, so I didn't want to rebuild it.
Yes, I know you're handing over a repo
That's a big ask, so here's exactly what it gets:
- Read-only access.** It's a GitHub App with Contents and Metadata read-only. It can't change your code.
- Processed in memory.** Your source isn't kept.
- Your call on what it sees.** Install it on only the repos you choose.
Come break it
It's free, no credit card. If you want to try it:
https://docloom.babar-wealthpilot.workers.dev
I'm building this solo, so I mostly want to find out where it falls over. Tell me your stack in the comments and I'll run it on a sample repo and share what happens, good or bad.
Top comments (1)
As a new developer and solo developer , I want real feedback , I will surely appreciate that