doctor

Diagnose and fix oh-my-codex installation issues across Codex environments.

2|1|Updated Oct 8, 2009
One-click install
npx skills add https://github.com/riethmayer/dotfiles --skill doctor-riethmayer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/riethmayer/dotfiles/tree/main/stow/agents/.agents/skills/doctor
Command: npx skills add https://github.com/riethmayer/dotfiles --skill doctor-riethmayer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and fix oh-my-codex installation issues across Codex environments.

Core Features & Use Cases

  • Validate plugin version and cache state
  • Detect and clean legacy hooks and scripts
  • Verify AGENTS.md presence and OMX marker for config integrity
  • Guide migration to canonical skill roots and plugin-based delivery

Quick Start

Run the diagnostic to identify and fix installation issues.

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 with stale hooks and legacy scripts?

To diagnose oh-my-codex installation issues, run a diagnostic check that inspects configurations, detects stale hooks, and identifies legacy curl-installed scripts to fix installation problems.

What is the best way to clean legacy hooks and plugin caches in Codex environments?

The best way to clean legacy hooks and plugin caches is to run a diagnostic that detects stale legacy scripts, manages plugin caches, and guides migration to canonical skill roots.

How do I verify AGENTS.md presence and OMX marker for Codex config integrity?

You verify AGENTS.md presence and OMX marker for config integrity by running a diagnostic that checks the AGENTS.md status and validates plugin version and cache state.

Why does my oh-my-codex plugin version check fail after a legacy curl installation?

An oh-my-codex plugin version check fails when legacy curl-installed content conflicts with the canonical plugin delivery, requiring diagnostic inspection of legacy files and cache cleanup.

Can I use this diagnostic to migrate to canonical skill roots and plugin-based delivery?

Yes, you can use this diagnostic to guide migration to canonical skill roots and plugin-based delivery by identifying legacy scripts and verifying configuration integrity.