lcx-doctor
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.
npx skills add code-yeongyu/oh-my-openagent --skill lcx-doctor --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 `LAZYCODEX_SOURCE_ROOT` or `${TMPDIR:-/tmp}/lazycodex-sources`. 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 1. Materialize the latest sources under `LAZYCODEX_SOURCE_ROOT="${LAZYCODEX_SOURCE_ROOT:-${TMPDIR:-/tmp}/lazycodex-sources}"` first. Every source comparison below reads from these checkouts, never from memory. Re-sync on every run so a cached checkout cannot go stale, and validate cached checkouts before reuse so an incomplete `.git` directory cannot poison diagnosis: ```bash LAZYCODEX_SOURCE_ROOT="${LAZYCODEX_SOURCE_ROOT:-${TMPDIR:-/tmp}/lazycodex-sources}" mkdir -p "$LAZYCODEX_SOURCE_ROOT" valid_source_checkout() { DEST="$1" git -C "$DEST" rev-parse --is-inside-work-tree >/dev/null 2>&1 && git -
- Required Workflow
- Doctor Report Template
- Follow-up Routing
- Stop Conditions
mkdir -p "$LAZYCODEX_SOURCE_ROOT" git -C "$DEST" rev-parse --is-inside-work-tree >/dev/null 2>&1 && git -C "$DEST" config --get remote.origin.url >/dev/null 2>&1 if [ -e "$DEST" ] && ! valid_source_checkout "$DEST"; then mv "$DEST" "$QUARANTINED" echo "Moved corrupt source cache $DEST to $QUARANTINED" >&2 fi recover_corrupt_source_checkout "$DEST" if [ ! -d "$DEST" ]; then gh repo clone "$REPO" "$DEST" -- --depth=1 \
What does the lcx-doctor skill do?
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.
How do I install it?
Run `npx skills add code-yeongyu/oh-my-openagent --skill lcx-doctor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From code-yeongyu/oh-my-openagent, a repository with 67,209 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.