From repository to reviewed fix.
One pipeline, eight stages. Here's what happens to your docs on every run, with real numbers from our run on Project B (an open-source AI SDK with a large docs site), the largest of the three projects we tested.
Source
1 repositoryConnect a repository through the GitHub App, or point the CLI at a local checkout or a public Git URL. Clones are shallow, go into a temporary directory, and are deleted when the run ends.
Detect
mintlify · 261 pagesIdentify the docs framework from its config (mkdocs.yml, docs.json or mint.json, docusaurus.config.*, ReadMe exports) and collect every Markdown and MDX page in the docs tree.
Extract
1327 code blocksPull out every fenced code block with its language, line number, the page it belongs to, and any output block shown right after it. Tabbed code groups (npm / yarn / pnpm, Python / JS) are recognized as alternatives.
Plan
927 to test · 400 skipped with reasonsDecide per block: execute, syntax-check, or skip with a stated reason. Infer install steps the page documents, keep blocks in page order so later snippets see earlier variables, and pick one variant from each tab group.
Run
406 passed · 520 failed · 290s totalExecute in a fresh container per page: unprivileged user, read-only root filesystem, all Linux capabilities dropped, no privilege escalation, memory, CPU, process and time limits. gVisor is supported for an extra kernel boundary.
Triage
7 likely docs bugs out of 520 failuresClassify each result into one of 24 categories by matching the actual error, not the exit code alone. Context-dependent fragments, missing credentials and network flakiness are kept out of the docs-bug count by design.
Fix & verify
verified before it's proposedFor each likely docs bug, draft the smallest change that makes the example work, using your chosen model provider. Re-run the fixed page in the sandbox and keep the fix only if it passes.
Report
you review and mergePublish a check run with line annotations, a Markdown and JSON report, the docs badge, and one draft pull request per affected page. Nothing merges without a maintainer's approval.
Metrics: DocsAlive v0.2.1 on Project B, October 19, 2026. Stage 07 drafts fixes only when a model provider is configured. The run above was triage-only.
Triggered by the moments docs break.
On pull requests
Changes to docs or code get a check run before merge, with annotations on the exact lines that fail.
On releases
Tag a release and every example is re-tested against the version you just shipped.
Nightly
Your docs install third-party packages too. Nightly runs catch drift when they change, not when a customer does.
What a single run looks like
The same engine powers the CLI, the GitHub App and the free Health Check. This is the real summary line from our Project C run. It flagged zero docs bugs, which is a useful result too: none of the 45 failing blocks were escalated, because each was classified as a fragment, a credential-gated example or TypeScript-only syntax.