omc-doctor

Diagnose oh-my-claudecode installation issues by inspecting Claude configuration and cached plugin versions.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/dropsyoon/oh-my-claudecode --skill omc-doctor-dropsyoon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omc-doctor
Source: https://github.com/dropsyoon/oh-my-claudecode/tree/main/skills/omc-doctor
Command: npx skills add https://github.com/dropsyoon/oh-my-claudecode --skill omc-doctor-dropsyoon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly identify why oh-my-claudecode (OMC) isn’t working correctly by checking plugin versioning, legacy configuration conflicts, and stale cache state in your Claude environment.

Core Features & Use Cases

  • Installation diagnostics: Detect missing, outdated, or multiple cached versions of the OMC plugin to pinpoint why behavior doesn’t match expectations.
  • Legacy conflict detection: Flag outdated settings.json hook entries and legacy hook scripts that can cause duplicate or inconsistent command/agent/skill behavior.
  • Claude.md integrity checks: Verify OMC markers and detect version drift between deterministic Claude sources and cached plugin versions.
  • Cleanup guidance for legacy installs: Identify legacy agent/command/skill directories that were previously installed outside the plugin system, reducing confusion and conflicts.

Quick Start

Run the omc-doctor skill to generate an OMC Doctor Report and see what to fix in your Claude Code setup.

Frequently Asked Questions about omc-doctor

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

FAQPage Schema
Why is my Claude Code plugin not working after updating oh-my-claudecode?

Claude Code plugin issues often stem from version drift between CLAUDE.md and cached OMC plugin artifacts. Diagnosing the installation inspects local Claude configuration directories and cached plugin versions to pinpoint mismatches causing the malfunction.

How do I diagnose duplicate agent or command behavior in Claude Code?

Diagnose duplicate Claude Code behavior by detecting legacy hook scripts and outdated settings.json entries. Inspecting your environment for pre-plugin agent, command, and skill directories identifies conflicts caused by old installations running alongside the current plugin system.

How do I check for legacy hook conflicts in my Claude configuration?

Check legacy hook conflicts by scanning Claude configuration directories for outdated settings.json hook entries and old hook scripts. A structured diagnostic report flags these legacy configurations that cause inconsistent command and agent behavior.

What causes cache invalidation issues with Claude Code CLI plugins?

Cache invalidation issues with Claude Code CLI plugins are caused by multiple or stale cached plugin versions. Checking the local plugin cache reveals outdated artifacts that fail to match the expected deterministic Claude sources.

Does oh-my-claudecode installation troubleshooting require specific environment variables?

Oh-my-claudecode installation troubleshooting reads the CLAUDE_CONFIG_DIR environment variable to locate your configuration, falling back to ~/.claude if unset. It requires filesystem read access to inspect CLAUDE.md files and cached plugin artifacts.