Skip to main content
Doctorine

CLI

The release workflow, from your terminal.

Validate, compare, publish, inspect, and manage Doctorine from local development or CI with stable JSON output, frozen exit codes, and idempotent writes.

Start free Explore the command map
doctorine · payments-api main 
❯ doctorine compare

  content     3 pages changed
  api model   2 operations changed
  sdk impact  typescript · python · go

❯ doctorine publish --json
{"release":"rls_0138","status":"live"}

❯ doctorine status
  portal      live
  sdk builds  3 verified
  skill       ready
Exit 0 Stable JSON · CI-safe

Control Doctorine from local development and CI.

Human-readable commands and stable machine output cover the same workflow without maintaining a second automation layer.

  • Local validation and release comparison

  • Platform administration and Git conflict tools

  • SDK, MCP, and Agent Skill generation

More than a publish command.

The CLI covers the work that otherwise sends an engineer back to several settings screens: content, releases, project administration, generators, and agent setup.

Content
validate · compare · pull · push
Release
publish · status · logs · versions
Platform
domains · branding · tokens · members
Artifacts
sdk generate · sdk diff · skill · mcp

Human-readable by default. Machine-stable when it matters.

Terminal output explains the next action to a person. JSON mode and stable exit codes give CI and agents the same result without scraping prose.

doctorine sdk diff --jsonExit 2 · drift
{
  "project": "payments-api",
  "target": "typescript",
  "status": "drift",
  "changedMethods": 3
}

Set up the interfaces agents need from the same tool.

Generate a runnable MCP package for your API, build an Agent Skill, or install Doctorine’s remote workspace MCP into a supported coding client. 

❯ doctorine mcp install --client codex
Configured Doctorine workspace MCP

❯ doctorine sdk generate --target skill
Wrote payments-api-skill.zip

Automation uses the same platform state.

Commands operate on the same projects, permissions, revisions, and conflict rules as the dashboard.

  • Local development

    Validate, compare, pull, push, generate, and inspect changes before a hosted release is involved.

  • Continuous integration

    Use stable JSON, frozen exit codes, explicit CI mode, and idempotent writes to make automation reviewable.

  • Platform operations

    Publish, inspect logs, manage versions, domains, branding, service tokens, members, and Git conflicts from the same authenticated surface.

Automation has a stable contract.

Frozen exit codes, JSON schemas, and idempotent writes make failures understandable and retries safe.

One public API
The CLI drives the same versioned API and permissions as the dashboard instead of maintaining a shadow control plane.
Automation contract
Structured output and documented exit behavior make success, drift, validation failure, and remote failure distinguishable in CI.
Repository targeting
A repo-local project target keeps commands explicit and repeatable across contributors and build agents.

Put the release workflow where engineers already work.

Authenticate once, target a project, and inspect the same state your team sees in the dashboard.

Start with the CLI