doctor

Diagnose oh-my-codex installation issues and validate Codex CLI plugin configuration.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/pextacy/stellar --skill doctor-pextacy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/pextacy/stellar/tree/main/skills/doctor
Command: npx skills add https://github.com/pextacy/stellar --skill doctor-pextacy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Oh-my-codex installation or configuration issues can block development workflows. This skill helps identify and resolve those problems by performing a structured diagnostic.

Core Features & Use Cases

  • Checks plugin version health, including installed and latest releases.
  • Validates configuration integrity across config.toml and legacy settings.json, and detects problematic hook references.
  • Detects stale or conflicting script artifacts and provides guidance for cleanup and recovery.
  • Use Case: When Codex stops working after an update, run this skill to surface misconfigurations and recommended fixes.

Quick Start

Run the doctor skill to scan your Codex setup and generate a diagnostic report.

Frequently Asked Questions about doctor

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

FAQPage Schema
How do I diagnose oh-my-codex installation issues after an update breaks my Codex CLI?

Fix Codex configuration errors by validating config.toml and legacy settings.json, detecting problematic hook references, and applying optional auto-fix guidance to restore your development environment workflow.

What does a Codex plugin health check look for when troubleshooting misconfigurations?

Clean up stale Codex script artifacts by detecting conflicting legacy files during a diagnostic scan, which provides targeted guidance for artifact removal and environment recovery.

Can I use a diagnostic skill to fix legacy settings.json and config.toml conflicts in Codex?

Run a diagnostic scan on your Codex setup to generate a diagnostic report that surfaces misconfigurations, stale artifacts, and version health issues with recommended recovery actions.

Why does Codex stop working when stale script artifacts conflict with my current plugin version?

Check your Codex plugin version state by comparing installed and latest releases during a diagnostic scan, which surfaces version mismatches and configuration issues blocking your CLI.