Docs that track your code, push by push.
Wire up a repo. Every merge to main runs a generation. You wake up to a PR (or a draft you can review in the dashboard) and the AI has already explained what changed.
The working loop
Set it up once. Keep the knowledge moving.
- 01
Connect a repo
Install the GitHub App on a repo, or upload a zip if you want to test without granting any access. We index the repo once and listen for pushes to your default branch.
- 02
AI generates
A push starts a section-aware synthesis that reads the relevant code and updates the documentation structure you configured.
- 03
Output lands
You wake up to an opened PR (or to drafts in the dashboard, your call). Review or accept and you have docs that track the code.
Triggered by your code
GitHub-native, no manual runs.
Install the CodeSummary GitHub App and choose the repositories that belong to the product. Changes on the default branch can then keep the knowledge current automatically.
There are no workflow files to maintain in each repository. Your team controls the update depth, whether changes run automatically, and whether the result becomes a dashboard draft or a reviewable pull request.
Section-aware
Different docs need different prompts.
A marketing landing-style page and a developer error-codes reference look nothing alike. We let you pick what your site includes from a small, opinionated set: General Overview, Usage / User guides, Marketing material, Developer docs.
Each section runs through a different prompt and produces a different shape. The developer section auto-includes an interactive OpenAPI reference when we detect a spec; the marketing section uses landing-page rhythm rather than reference rhythm.
Combine the four sections however you want, or pick one of the named presets we ship with: API docs site, User help center, Marketing site, Full SaaS.
Audience-aware
Same code, different reader.
Tell us who you're writing for: End users, Developers, Admins / Operators, or Mixed. The synthesis pipeline shifts tone and depth based on the answer.
End-user docs use plain language, walk through tasks, and stay short. Developer docs assume technical baseline, show code, and detail edge cases. Mixed is the safe default if you can't pick.
Multi-repo per site
Stitch together as many repos as you want.
You don't have a monorepo. Your billing service is one repo, your auth service is another, your dashboard is a third. A CodeSummary site can pull from all of them at once.
The synthesizer reads across the linked repos as one logical product. Add a new repo, the next regeneration picks it up. Remove one and the docs about it drop out.
OpenAPI spec extraction
An API reference, with or without a spec.
If your code ships with an OpenAPI document, we preserve it and include an interactive reference in the developer section.
If it doesn't, we synthesize one from your route handlers and types. You get the same interactive reference at the bottom of the docs without writing a single YAML file. The synthesized spec is fully editable from the dashboard's spec editor; edits stick across regenerations.
Manual uploads
Test the platform without granting access.
Not ready to install the GitHub App? Drag a zip of your repo into the dashboard. We treat it as a source the same way we treat a GitHub repo, run the same pipeline, produce the same output.
Useful for evaluations, demos, and private repos that you don't want to grant CodeSummary persistent access to.
Put it to work
Turn the next code change into useful knowledge.
Start with one repository. Review the result before anything is published.