Frontend developer
Auto-document every React component PR with type-aware drafts. No more out-of-sync prop tables.
docs-keeper*
Merge a PR and docs-keeper opens a documentation PR for you to review — grounded in your actual diff, so it can't invent APIs that don't exist. Right inside GitHub.
Free for public repos · We run it on our own repos · You review every change
- 7 validation gates
- ~27s merge → PR
- $0.004 / doc PR
- Free for public repos
No new dashboard
It all happens inside your GitHub.
You merge a pull request. Before you've closed the tab, docs-keeper has already posted back — as a real PR, a real check, a real fix.
- A documentation PR opens itself — in your team's voice.
- A critical vulnerability is found and fixed in the same flow.
- Seven validation gates pass as native GitHub checks.
github.com/your-org/api · pull/1482
feat: rotate refresh tokens on /auth/refresh #1482
Mergedjordanwants to merge into→
mainfromfeat/token-rotationdocs-keeper[bot]botcommented · just now
📝 I opened #1483 with the docs for this change — updated auth.mdand the API reference, in your team's voice.
🛡️ Security scan: 1Critical found & fixed in #1484.
All checks have passed· 3 successful checks
docs-keeper / draft-docs— doc PR #1483 opened
docs-keeper / 7 validation gates
docs-keeper / security-scan— 0 critical remaining
How it works
Three steps. Then it runs on its own.
Install once. From then on, every merge becomes a documentation PR — and a security fix when it finds one — without anyone opening a new tool.
01
Install from GitHub
One click from the Marketplace. docs-keeper asks only for the scopes it needs — readable before you approve.
docs-keeperbot
Docs + security scanning
02
Merge a pull request
Keep shipping exactly how you do today. The moment a code PR merges, a run kicks off — in ~27 seconds, for fractions of a cent.
Mergedfrom
feat/token-rotation #1482 merged · run started
03
Get a doc PR + a fix PR
docs-keeper posts back inside GitHub: a documentation PR in your voice, plus a fix PR for anything its scan flags — each as a native check.
- doc PR #1483 · opened
- fix PR #1484 · critical resolved
FEATURE 01
An Auto-Doc-First Experience
Every merged PR becomes a documentation PR. No manual writing. Ever.
7 validation gates
Checked before you ever read it.
Every documentation PR clears seven gates — link integrity, compiling code samples, terminology, voice match, redaction, freshness, and clean rendering. They run as ordinary GitHub checks, so a doc PR only reaches you when it's already green.
No unreviewed prose ever lands — the gate is the reviewer that never gets tired.
All checks have passed· 7 successful checks
gate / links resolve
gate / code samples compile
gate / terminology consistent
gate / voice match— 0.94 similarity
gate / no secrets · PII
gate / freshness
gate / renders clean
Security scanning · same PR
It doesn't just flag it. It fixes it.
docs-keeper scans every merged diff, posts findings as native code-scanning alerts, then opens a fix PR — and re-runs the check until it's green.
scanning your-org/api…
Cloning repo
Resolving dependencies
Running rules engine
AI semantic pass
Posting results to PR
CriticalSQL injection via unsanitized query
CWE-89 · ghsa-detectedsrc/db/users.ts:42
ReachableExploit likelyIntroduced in #1455
const q = `SELECT * FROM users
WHERE name = '${req.query.name}'`;
return db.raw(q);
docs-keeper
github.com/your-org/api/pull/1484
fix: bump lodash 4.17.11 → 4.17.21 (CVE-2021-23337) #1484
Opendocs-keeper[bot]botwants to merge into→
mainfromdocs-keeper/fix/lodashpackage.json
@@ package.json @@
24-"lodash": "4.17.11",
24+"lodash": "4.17.21",
All checks have passed· 2 successful checks
security-scan / re-run— alert resolved
ci / tests
Linked to alert #7 · was Critical → now resolved
Before
3Critical7High12Medium5Low
After docs-keeper
0Critical0High2Medium5Low
27 → 7issues · 0 Critical remaining
push protection
$ git push origin mainremote: error GH009: Secrets detected! This push failed.remote: — AWS key in src/config.ts:8remote: docs-keeper blocked the leak before it shipped.
Why developers trust it
Specific, verifiable, and honest about the machinery.
No vanity numbers. These are real engineering facts about how docs-keeper reads your code and protects it.
40+languages parsed
Tree-sitter AST-aware chunking — not arbitrary token windows.
−67%retrieval failure
Anthropic’s published Contextual Retrieval + reranking result vs. naive embeddings — the technique docs-keeper uses.
Sandboxedevery code example
Every snippet is compiled in a sandbox before the PR is opened.
0training on your code
Your repos are never used to train models. Read once, never stored.
Every merged PR comes back as a documentation PR — drafted in your team's voice, checked through seven gates, and opened for your review. It never auto-merges.
You approve every change. No new dashboard to babysit.Trusted with repo access
- Read once — never stored or used for training
- We scan ourselves — clean
- Least-privilege scopes, readable before install
Built for the way you ship
From a solo side project to a compliance-bound monorepo.
docs-keeper meets developers where they already work — the workflow doesn't change, the docs just stop drifting.
Backend engineer
API endpoints stay documented automatically. Every route change opens a docs PR before the next deploy.
Open-source maintainer
Contributors merge; docs-keeper updates the README and CHANGELOG. Your project docs scale without your bandwidth.
Enterprise developer
Brand-voice locked, audit logs, least-privilege scopes. Internal docs finally stay current with the codebase.
Plugs into the workflow you already use.
docs-keeper writes markdown into your repo — so it works with the source control and docs renderer you already have.
Source control
GitHub
Install the GitHub App — doc PRs open on a docskeeper/run-<id> branch, never your default branch.
Docs renderer
Mintlify
Renders the markdown docs-keeper writes into your repo.
Docs renderer
Docusaurus
Renders the markdown docs-keeper writes into your repo.
Docs renderer
MkDocs
Renders the markdown docs-keeper writes into your repo.
Docs renderer
ReadMe
Syncs from your repo — docs-keeper opens the PRs that update it.
Model routing
OpenRouter
Pro and above can route drafts to a custom model via OPENROUTER_MODEL.
Not a docs host. A docs author.
Hosting tools render your docs. docs-keeper writes the updates that go into them — reacting to every merge, in a PR you review.
Reacts to merges
A merged PR triggers a follow-up docs PR automatically — no human presses "generate".
You review the PR
Updates land on a docskeeper/run-<id> branch as an ordinary PR. Your default branch is never touched.
In your team's voice
Brand-voice memory drafts updates that read like your team already writes.
Hallucination gate
A 7-rule validation gate blocks bad drafts before a PR is ever opened.
Pricing that scales with you.
Simple tiers based on automation volume. Start free, upgrade when you grow.
Frequently asked questions
The technical details on how docs-keeper works with your stack.
Only on a branch named `docskeeper/run-<id>`, and it opens a PR you review like any other contributor. We never push to your default branch.
Not ready to install yet?
Get the occasional build-in-public update and launch note. No spam, unsubscribe anytime.
Ready when you are
Docs that keep themselves. Security that fixes itself.
All of it lives where your code already does — GitHub. Nothing to paste, nothing to babysit. Free for public repos.