adapto-doctor

adapto:doctor

Read-only health check for the Adapto CMS toolchain. It never changes anything — it reports what's wrong and the exact command to fix each item. It ships global + per-repo: run it anywhere to check the environment, or inside a project to also check project wiring.

When to use

• Any Adapto CLI command failed and you're not sure why (auth? tenant? CLI missing?).
• Before adapto:scaffold or any mutating skill, to confirm preconditions.
• After adapto auth login or switching tenants, to confirm the session is good.
• Triggers: "adapto doctor", "is my adapto setup ok", "why is adapto failing", "check my adapto environment".

When not to use

• To fix things — doctor only diagnoses. It prints fixes; the user (or another skill) runs them.
• As a precondition gate inside other skills — call the relevant CLI check directly; doctor is for humans.

Inputs

• None required. Optional mode flags on the check script:
  • --repo force project checks · --global skip them · (default: auto — project checks run if a package.json is present in the cwd).
  • --json machine-readable output.
  • --strict exit non-zero when a check fails (for shell gating). Off by default.

Outputs

• A checklist (✓ pass / ⚠ warn / ✗ fail) with a one-line detail and a fix hint per non-passing item, plus a pass/warn/fail tally.
• --json: { ok, mode, checks:[{id,label,status,detail,fix}], summary:{pass,warn,fail} }.
• Exit code 0 on a successful run (a report was produced) — doctor is a diagnostic, so a failing check is data, not a tool error. Read the JSON ok field (or the ✗ rows) for health. Pass --strict to make failing checks exit 1 for shell-level gating.

Checks

Environment (always):

1. cli_installed — adapto on PATH (else: install hint).
2. cli_version — version ≥ requires.cli (warn if older/unparseable). This is the floor: will the skills run at all.
3. cli_current — the installed CLI vs. the latest release tag (git ls-remote --tags on the CLI repo, not the rate-limited GitHub API). This is drift, not a floor: the CLI is pre-1.0 and its command surface moves between releases, so being behind shows up as a missing flag rather than an obvious "you're old". Behind → warn + the upgrade command, which the agent should offer (a §9 consent gate — it replaces a binary on PATH), never run silently. Never a fail. Offline → warn, same 5s cap as below.
4. pack_current — the installed skill pack vs. the latest main. The plugin sets no version, so Claude Code keys its cache on the git commit SHA (one commit = one version); this compares the installed SHA (from Claude Code's own installed_plugins.json) against git ls-remote <pack repo> refs/heads/main. Behind → warn + the update commands. Omitted entirely in a dev checkout (no install record) and if the pack ever adopts an explicit semver. Network failure is a warn, never a blocker — the call is capped at 5s so a diagnostic can't hang on an unreachable GitHub.
5. auth_valid — adapto auth me succeeds (shows the account email — identity, not a secret).
6. api_reachable — adapto status succeeds (gated on auth). A permission/403 error on this check is downgraded to a warn, not a fail: auth already proved the backend is reachable, so it's not a blocker for content work.
7. tenant_selected — an active tenant exists via adapto auth orgs, and its enabled languages are surfaced (this is also the canonical locale list per conventions.md §5). ℹ️ This reports the currently-active tenant; it is not an instruction to use it — work skills must still confirm the working tenant before scoped writes (don't assume the active one — conventions.md §12).