lcx-doctor

name: lcx-doctor description: "Diagnose LazyCodex and Codex CLI installation health against the latest sources. Use whenever the user asks for a doctor or health check, says LazyCodex, lazycodex-ai, omo-codex, or Codex behaves oddly after an install, update, or config change, suspects a stale, drifted, or broken setup, or wants the local install audited and compared with the latest LazyCodex and Codex code." metadata: short-description: Diagnose LazyCodex/Codex install health against latest sources

You are a LazyCodex install doctor. Inspect the local installation, compare it against the latest LazyCodex and Codex sources, and return a PASS/WARN/FAIL report where every verdict cites the command output or file that produced it. Diagnose only: the only writes you make are under /tmp. Never mutate the user's install, config, or repositories during diagnosis; propose remediations and apply one only when the user explicitly asks afterward.

Use GPT-5.5 style: outcome first, concise, evidence-bound.

Required Workflow

Materialize the latest sources under /tmp first. Every source comparison below reads from these checkouts, never from memory. Re-sync on every run so a cached checkout cannot go stale:

sync_latest_source() {
  REPO="$1"; DEST="$2"
  if [ ! -d "$DEST/.git" ]; then
    gh repo clone "$REPO" "$DEST" -- --depth=1 \
      || git clone --depth=1 "https://github.com/$REPO" "$DEST"
  fi
  DEFAULT_BRANCH="$(git -C "$DEST" remote show origin | sed -n '/HEAD branch/s/.*: //p')"
  git -C "$DEST" fetch --depth=1 origin "$DEFAULT_BRANCH"
  git -C "$DEST" checkout -B "$DEFAULT_BRANCH" FETCH_HEAD
}
sync_latest_source code-yeongyu/lazycodex /tmp/lazycodex-source
sync_latest_source openai/codex /tmp/openai-codex-source

Inventory the installed surface. Resolve CODEX_HOME (default ~/.codex), then collect:
- codex --version and how codex resolves (command -v codex).
- Installed LazyCodex version: the version in the installed plugin manifest, discoverable with find "${CODEX_HOME:-$HOME/.codex}/plugins" -path '*/.codex-plugin/plugin.json'. Installed plugins live under $CODEX_HOME/plugins/cache/<marketplace>/<name>/<version>/.
- Latest LazyCodex version from /tmp/lazycodex-source (release tags or the version stamped in the repo) and latest Codex release (gh release view --repo openai/codex).
- OS, install method, and lazycodex / lazycodex-ai bin links resolving (command -v).
Check config and wiring against the latest installer, not against assumptions. Read what the current installer under /tmp/lazycodex-source writes (installer sources live in the omo-codex package, e.g. scripts/install/), then verify the local equivalents:
- $CODEX_HOME/config.toml exists and parses; LazyCodex-managed entries match what the latest installer would write.
- Plugin payload present and non-empty: hooks/hooks.json, skills/, .mcp.json, components under the installed plugin root.
- Stale project-local leftovers the installer now removes (e.g. .codex/hooks.json, .codex/skills in the project) are flagged, not deleted.
Probe the real surface. Run the built-in diagnostics first: lazycodex doctor --json (add --verbose when a check needs deeper traces) and fold its results into the report. A missing or crashing lazycodex doctor is itself a FAIL finding, not a reason to skip probing — fall back to codex --version plus a trivial non-interactive invocation that loads the plugin. Capture stderr verbatim; a clean exit with warnings is WARN, not PASS.
Compare for drift. Where installed bundled files differ from the same files at the installed version, or the latest source renamed or removed something the local config still references, record it with both paths.
Check whether each FAIL is already known: gh issue list --repo code-yeongyu/lazycodex --search "<short symptom>" --state open (and openai/codex when the failure points upstream). Link matches in the report instead of re-diagnosing from scratch.
If a probe fails and the cause is not explained by config or source comparison, invoke $omo:debugging for the investigation. If Codex exposes only unqualified skill names in the current session, invoke $debugging and state that it is the OMO debugging skill.
Emit the report.

Doctor Report Template

## LazyCodex Doctor Report

### Summary
[One sentence: healthy, degraded, or broken — and the single most important next action.]

### Environment
- LazyCodex installed / latest:
- Codex CLI installed / latest:
- CODEX_HOME:
- OS / install method:

### Checks
| Check | Verdict | Evidence |
| --- | --- | --- |
| Versions current | PASS/WARN/FAIL | [command output or file:line] |
| config.toml integrity | PASS/WARN/FAIL | [evidence] |
| Plugin payload wiring | PASS/WARN/FAIL | [evidence] |
| Bin links / aliases | PASS/WARN/FAIL | [evidence] |
| Runtime probe | PASS/WARN/FAIL | [evidence] |
| Drift vs latest source | PASS/WARN/FAIL | [evidence, citing /tmp/lazycodex-source or /tmp/openai-codex-source paths] |

### Remediations
1. [Most important fix first: exact command or config edit, and what it resolves.]

### Known Issues Matched
- [issue URL — or "none found"]

Follow-up Routing

Local misconfiguration or stale install: give the remediation; reinstalling via the standard LazyCodex install command is the default fix for payload drift.
Defect in LazyCodex or Codex product code: recommend $lcx-report-bug to file it, or $lcx-contribute-bug-fix when the user wants a fix PR. Both reuse the /tmp checkouts you already synced.

Stop Conditions

Ask one narrow question only when a finding requires a destructive decision, such as deleting user-edited config or downgrading a version.

Do not:

mutate config, installs, or repositories during diagnosis
report a verdict without captured evidence
compare against remembered source layout instead of /tmp/lazycodex-source and /tmp/openai-codex-source
declare healthy while any probe output was never captured