Next.js codebases move fast: route groups get reorganized, server actions replace API routes, and config changes ripple through the app. docs-keeper parses your TypeScript with Tree-sitter so it understands the actual shape of your code, not just the diff text.
Docs that keep up with your App Router
docs-keeper reads your route handlers, server actions, and components — then updates the docs the moment a PR merges.
What docs-keeper keeps in sync
README & setup guides
Env vars, scripts, and install steps stay accurate as package.json and config evolve.
API route docs
Route handlers and server actions documented from their real signatures and return types.
Component usage
Exported component props and examples updated when interfaces change.
Migration notes
When you move from Pages to App Router, drafts flag what changed for consumers.
Docs it writes for Next.js
README.mdAPI referenceComponent docsCHANGELOG.mdArchitecture notes
Frequently asked
Does it understand the App Router?
Yes. docs-keeper parses TypeScript/TSX with Tree-sitter, so route groups, layouts, server actions, and client/server boundaries are all visible to the retrieval pipeline.
Will it touch my source code?
No. docs-keeper only opens documentation pull requests. It never pushes to your default branch and never auto-merges.
What about monorepos?
You configure which paths to include and exclude per repo, so a Turborepo or pnpm workspace only gets docs for the packages you opt in.
Try docs-keeper on your Next.js repo
One public repo, 20 doc PRs per month, no credit card. See if drafts read like your team before committing to a paid plan.