Developer Tooling
Autonomous Documentation Generator
Analyzes code structure, function signatures, and runtime behavior to generate README files, API docs, and inline comments.
The problem
Documentation falls out of sync with code because engineers update source faster than they update prose docs.
- New hires ping the team in Slack because the README describes last quarter's API.
- Nobody wants to be the one who blocks a PR over missing docs.
- The docs site says one thing; the code does another, and no one notices until support does.
What NEO built
NEO built an agent that parses repos with AST-aware (tree-sitter) analysis, generates README and API docs from inferred signatures, and only regenerates pages affected by a diff, opening PRs directly in CI.
The result
4 languages, diff-aware
Keeps README, API reference, and architecture docs automatically synchronized with the current codebase, with zero manual upkeep.
From the blog · 8 min
AutoDoc: An Autonomous Agent That Reads Your Codebase and Writes the Docs
NEO built AutoDoc, an autonomous documentation agent that analyzes code structure, function signatures, class hierarchies, and runtime behavior to generate README files, API docs, and inline comments.
Try this in your workspace
Paste this into NEO chat to kick off the same workflow on your own data.
Set up an agent that parses my repo with tree-sitter, generates README and API docs from the actual function signatures, and opens a PR with just the docs affected by my latest diff.
Paste it in · review the plan · get the diff
Get NEO
