GitDocu ingests your entire repository context to keep docs synced and catch logical regressions before they merge. Stop relying on outdated READMEs.
Now in private beta · Read-only repository scopes · Free for open source
~/acme/payments-api on feat/session-refactor
❯ gitdocu audit --pr 482 --depth=full
▸ Fetching PR #482 "Refactor session middleware" (6 files, +214 −87)
▸ Parsing AST across 1,284 files ·················· done 2.1s
▸ Packing context 412,870 / 1,000,000 tokens ······· done
▸ Reasoning over cross-module call graph with Claude ··· done 31.7s
✖ Security · Blocking src/auth/session.ts:41
Revocation check removed from validateToken(). Revoked JWTs will now pass.
40export async function validateToken(token: Token) {
41- if (await revocations.has(token.jti)) return null;
42 return verifySignature(token, env.JWT_SECRET);
43}
3 downstream callers assume revoked tokens are rejected:
⚠ Doc drift docs/architecture/auth.md still describes edge-less revocation flow
✓ Review comment + suggested fix posted to PR #482
✓ Doc patch opened as gitdocu/sync-auth-md
2 findings · 1 blocking · completed in 38.4s
❯
Illustrative example. The repository, code and findings shown are fictional.
Why Claude?
ESLint, SonarQube and static analyzers are excellent at syntax and style — but they evaluate one file, one rule at a time. They can't tell you that removing a guard in auth/ silently breaks an invariant your billing/ module depends on.
GitDocu applies LLM reasoning across up to 1,000,000 tokens simultaneously — source, dependency graph, existing docs and the PR diff in a single pass — so it reasons about your architecture the way a senior reviewer would.
Features
Three capabilities, one shared understanding of your repository.
Every commit triggers a diff-aware rewrite of affected Markdown pages and Mermaid.js diagrams — so your architecture docs describe the code that's actually running.
GitDocu maps each change against the full call graph to surface cross-module impact — broken invariants, unsafe refactors and security regressions — before a human reviewer opens the diff.
Ask anything about your codebase in plain English. Every answer is grounded in source, with precise file and line-number citations you can click straight into.
How it Works
STEP 01
Install the GitHub App with read-only scopes, or point any Git host's webhook at GitDocu.
STEP 02
We parse your repo into syntax trees, rank symbols by relevance to the change, and pack the densest possible context.
STEP 03
Claude reasons over up to 1M tokens at once, tracing data flow and contracts across every module the change touches.
STEP 04
Findings land as inline review comments, and updated Markdown & diagrams arrive as a ready-to-merge PR.
Pricing
Free forever for open source. Upgrade when your team needs architectural reviews.
GitDocu is in private beta. Plans and prices reflect our planned launch and may change.
For open-source maintainers and side projects.
$0 /mo
Join the betaFor product teams shipping to production daily.
$29 /dev/mo
Request Early AccessFor regulated orgs with strict data residency needs.
Custom
Contact salesPrivate Beta
We're onboarding a small group of engineering teams to the private beta. Send us a short note and we'll get back to you personally.
Email us at
To help us prioritize, include:
We only use your details to respond and manage beta access. See our Privacy Policy.