Documentation
Share code or describe a feature and Seba writes the docs — README, how-to guide, reference, or an update to what you have — in a friendly, user-forward voice. You get the docs back as a file to commit. Billed per run.
Docs a smart newcomer can follow, not a code dump
Structured by what readers need
Seba maps your docs to the right types — tutorial, how-to, reference, explanation — so a reader gets the learning path, the task recipe and the lookup, not one wall of text.
User-forward voice
Every section leads with what the reader can do, not implementation detail. “You can now…” not “Refactored the…”. Written like you’re explaining to a smart person who hasn’t seen the code.
Examples that actually run
Code samples are copy-paste-complete — real auth, real error handling, the whole task — not a hello world that lies about the hard parts.
Just share the code
Paste a file, send a public repo URL, or describe the feature in Telegram. The docs come back as a file you commit, billed per run.
What Seba can document
The Diataxis framework — the four doc types every project needs.
- README — what it is, install, quickstart, usage, links to deeper docs
- Tutorials — a learning path that takes a newcomer from zero to working
- How-to guides — task recipes for the things users actually do
- Reference — every command, flag, function and option, looked up fast
- Explanation — the why behind the design, the model, the tradeoffs
- Changelog — release notes in a voice that sells what users can now do
- Migration & upgrade notes — what changed and how to move across it
- Cross-doc consistency — discoverable, no contradictions, one source of truth
From code to docs in three steps
Open Seba in Telegram
One tap into @meetseba_bot. No install, no signup forms.
Share the code or feature
Paste a file, send a public repo URL, or describe it. “Write a README and quickstart for this CLI.”
Get the docs
Seba writes structured, user-forward docs and returns them as a file you commit, with the exact credit cost shown up front.
When to write or update docs
Close the gap between what shipped and what’s written.
- +A new feature shipped with no docs yet
- +The README drifted out of date with the code
- +A library needs a real quickstart and reference
- +An internal tool only one person knows how to run
- +Release notes need a voice users actually read
- +Onboarding docs a new contributor can follow cold
Frequently asked questions
What kinds of docs can Seba write?+
README, tutorials, how-to guides, reference, explanation, changelog and migration notes — structured with the Diataxis framework so each reader need is covered.
Does Seba commit the docs to my repo?+
No. Seba returns the docs as a file. You review and commit them. Seba writes from what you share and does not push to your repository or access private systems.
What does Seba write from?+
Pasted code, a public repo URL, or a description of the feature. The more you share, the more accurate the docs — Seba documents what it can see.
Can it update existing docs instead of starting over?+
Yes. Share the current docs and the code that changed, and Seba updates them to match what shipped, preserving your structure and voice.
What format is the deliverable?+
A Markdown file ready to drop into your repo. Ask for separate files per doc type or a single README and Seba formats it that way.
How much does it cost?+
You spend credits per run, and Seba shows the exact cost before it starts. Start free with welcome credits; credits never expire.
Get your docs written in a single message
Share code with Seba and get clear, user-forward docs back to commit. Pay only for the run.
No install · no signup forms