lcx-doctor

Diagnose LazyCodex/Codex installation health against latest upstream sources.

3.2k|198|Updated May 25, 2026

Search Tags:#drift-detection #installation #diagnose #health-check #codex-cli #diagnostic-report #lazycodex

Ready to run

npx skills add https://github.com/code-yeongyu/lazycodex --skill lcx-doctor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lcx-doctor
Source: https://github.com/code-yeongyu/lazycodex/tree/main/plugins/omo/skills/lcx-doctor
Command: npx skills add https://github.com/code-yeongyu/lazycodex --skill lcx-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses the health and readiness of a LazyCodex/Codex installation against the latest sources, surfacing PASS/WARN/FAIL findings with evidence to guide remediation.

Core Features & Use Cases

End-to-end diagnostic of LazyCodex/Codex setup, including source sync, config integrity checks, plugin payload validation, and surface runtime probes.
Generates a structured report with evidence and remediations, and identifies drift between local installation and upstream sources.
Use case: when a user experiences odd behavior after install/update/config change, run the doctor to verify health and get concrete next steps.

Quick Start

Run the doctor to generate a health report for the current LazyCodex/Codex installation.

Frequently Asked Questions about lcx-doctor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run a health check on my LazyCodex installation?▼

A diagnostic health check for LazyCodex syncs upstream sources to inventory your local install, verify config and plugin payloads, and run runtime probes. It outputs a structured report surfacing PASS, WARN, or FAIL findings with evidence and concrete remediations.

Why does Codex behave oddly after an update or config change?▼

Config drift between local and upstream sources causes odd behavior after updates. A diagnostic doctor materializes the latest sources locally, inventories your installation, and compares payloads to report exact drift with actionable remediations.

What is drift detection for a Codex CLI setup?▼

Drift detection for a Codex CLI setup compares local installations against latest upstream releases. It inventories installed components, validates config payloads, and reports discrepancies with evidence to guide remediation.

Does the LazyCodex doctor require any dependencies to diagnose installations?▼

No dependencies are required to diagnose LazyCodex installations. The doctor autonomously materializes necessary upstream sources under /tmp to inventory your setup and verify config integrity without prior manual configuration.

What is the best way to audit a LazyCodex config and plugin payload?▼

The best way to audit LazyCodex configs and plugin payloads is to run a diagnostic doctor. It validates config integrity, compares plugin payloads against upstream sources, and generates a structured report with evidence and remediations for detected drift.

What limitations should I expect when diagnosing Codex installation health?▼

Diagnosing Codex installation health relies on materializing upstream sources under /tmp, which requires sufficient local storage. The doctor detects drift and reports evidence-based findings rather than automatically applying fixes to your setup.