skills.rest
Orinks
OrinksCOMMUNITY
Explore all skills by this author →
GitHub

doctor

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

24|2|Updated Mar 12, 2025
Search Tags:#automation#troubleshoot#maintenance#installation#diagnose#oh-my-codex
One-click install
npx skills add https://github.com/Orinks/AccessiWeather --skill doctor-orinks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/Orinks/AccessiWeather/tree/main/.codex/skills/doctor
Command: npx skills add https://github.com/Orinks/AccessiWeather --skill doctor-orinks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses and fixes oh-my-codex installation issues to restore a healthy Codex CLI environment and reduce setup friction.

Core Features & Use Cases

  • Step-by-step diagnostic workflow that checks plugin versions, hook configurations, legacy Bash hooks, AGENTS.md configuration, plugin caches, and legacy installation artifacts.
  • Guidance to resolve common blockers for OMX in local and multi-user setups, including cleanup of legacy roots and outdated files.
  • Actionable fixes for detected issues, with safety reminders and rollback notes.

Quick Start

Run installation diagnostics to identify and fix common OMX setup issues.

Frequently Asked Questions about doctor

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

FAQPage Schema
How do I diagnose and fix oh-my-codex installation issues in my Codex CLI?▼

To diagnose oh-my-codex installation issues, run a diagnostic workflow that inspects plugin versions, hook configurations, AGENTS.md files, and legacy directories, then applies actionable fixes to restore a healthy Codex CLI environment.

What causes legacy hook conflicts during OMX setup?▼

Legacy hook conflicts during OMX setup are caused by outdated Bash hooks and legacy installation artifacts that interfere with the canonical skill root at ~/.codex/skills/, requiring diagnostic cleanup to resolve.

How do I clean up legacy directories and plugin caches for Codex CLI?▼

Clean up legacy directories and plugin caches by running the OMX diagnostic workflow, which inspects config.toml, identifies outdated files, and recommends automated fixes to ensure the canonical skill root is used.

Can I use this diagnostic workflow for multi-user Codex CLI setups?▼

Yes, you can use this diagnostic workflow for multi-user Codex CLI setups, as it provides guidance to resolve common blockers and cleanup legacy roots across different local and multi-user environments.

Does the OMX diagnostic tool automatically apply fixes to config.toml?▼

The OMX diagnostic tool recommends or applies automated fixes to config.toml and legacy settings, providing safety reminders and rollback notes to ensure safe restoration of the Codex CLI environment.

Why is my oh-my-codex installation pointing to the wrong skill root?▼

Your oh-my-codex installation points to the wrong skill root due to legacy installation artifacts and outdated directories, which the diagnostic workflow detects and corrects to the canonical ~/.codex/skills/ path.

Related Skills

Explore More Software Engineering Skills→
riethmayerriethmayer
2

hud

Read local .omx/state/*.json files and expose OMX HUD state via the omx hud CLI.

Community
Intermediate
Goblin1024Goblin1024
6

doctor

Diagnose and fix oh-my-kimi installation issues across local environments.

Community
Intermediate
koasis89koasis89

doctor

Detects and fixes oh-my-codex installation issues including plugin versions and legacy content.

Community
Advanced
sigridjinethsigridjineth
20

doctor

Diagnose and fix oh-my-codex installation and configuration issues.

Community
Intermediate