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.
lcx doctor 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 or . 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,…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/lcx-doctor · pinned to the source commit
# Run from your project root
git clone https://github.com/code-yeongyu/oh-my-openagent.git .skillboard-tmp
git -C .skillboard-tmp checkout d86d06e94fb4ba67ae5b451b96db7634af75de78
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/packages/omo-codex/plugin/components/lcx/skills/lcx-doctor" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/code-yeongyu/oh-my-openagent.git .skillboard-tmp
git -C .skillboard-tmp checkout d86d06e94fb4ba67ae5b451b96db7634af75de78
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/packages/omo-codex/plugin/components/lcx/skills/lcx-doctor" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/lcx-doctor
Scanner static-checks@0.1.0 · commit d86d06e94fb4. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
Instructs shell/process/package operations that run commands on the host.
Evidence: npm install· fingerprint 3a2dc0ae21eb56d7