omc-doctor

Diagnose oh-my-claudecode installation issues by validating plugin versions and config remnants.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/nichobbs/lyric-lang --skill omc-doctor-nichobbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omc-doctor
Source: https://github.com/nichobbs/lyric-lang/tree/main/.claude/skills/omc-doctor
Command: npx skills add https://github.com/nichobbs/lyric-lang --skill omc-doctor-nichobbs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node.

What problem does it solve?

It diagnoses and resolves common installation problems with the oh-my-claudecode (OMC) plugin in Claude Code, including missing or outdated plugin versions, legacy configuration conflicts, and stale caches.

Core Features & Use Cases

  • Plugin version diagnostics: Checks which oh-my-claudecode version is installed versus the latest available version and flags outdated or missing installs.
  • Legacy config & hook detection: Searches profile-level and project-level Claude configuration files for legacy "hooks" entries and legacy bash hook scripts that can cause duplicate or conflicting behavior.
  • CLAUDE.md integrity checks: Verifies OMC markers (OMC:START and OMC:VERSION), detects file-split companion patterns (e.g., CLAUDE-omc.md), and reports version drift against cached plugin versions.
  • Stale cache cleanup guidance: Identifies multiple cached plugin versions and recommends cleanup to ensure consistent behavior.
  • Optional legacy content cleanup: Provides safe removal steps for legacy curl-installed agents/commands/skills when they conflict with plugin-provided equivalents.

Quick Start

Run the omc-doctor skill and follow its steps to verify your OMC plugin version, CLAUDE.md markers, and any legacy hook/config conflicts.

Frequently Asked Questions about omc-doctor

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

FAQPage Schema
How do I fix oh-my-claudecode installation issues in Claude Code?

Fix oh-my-claudecode installation issues by validating installed plugin versions against the local cache, detecting legacy hook remnants in config files, and verifying CLAUDE.md OMC markers to report CRITICAL or WARN findings for automated remediation.

Why does my CLAUDE.md file show outdated OMC markers after updating the plugin?

Outdated OMC markers in CLAUDE.md occur due to version drift between your config file and the cached plugin version under ~/.claude/plugins/cache/. Diagnosing the issue checks OMC:START and OMC:VERSION markers against the local cache to detect mismatches.

How do I clean up legacy hooks and old configuration remnants in Claude Code?

Clean up legacy hooks in Claude Code by searching profile-level and project-level configuration paths for stale "hooks" entries and legacy bash hook scripts. Diagnostic steps identify these remnants and provide safe removal guidance to resolve conflicting behavior.

Does the omc-doctor diagnostic require Node to run installation checks?

Yes, the omc-doctor diagnostic requires Node as a dependency. It uses Node to read CLAUDE_CONFIG_DIR-resolved config paths, inspect plugin cache versions, and evaluate your local Claude Code environment for stale caches and missing configuration files.

What causes duplicate or conflicting behavior from oh-my-claudecode plugins?

Duplicate or conflicting behavior from oh-my-claudecode is typically caused by legacy curl-installed agents, commands, or skills conflicting with plugin-provided equivalents, alongside multiple cached plugin versions that prevent consistent execution.

oh-my-claudecode plugin not working, how do I check for stale caches?

Check for stale caches by inspecting the plugin cache directory at ~/.claude/plugins/cache/omc/oh-my-claudecode. The diagnostic identifies multiple cached plugin versions and recommends cleanup to ensure your oh-my-claudecode installation behaves consistently.