omc-doctor

Diagnoses oh-my-claudecode installation issues by checking plugins, legacy hooks, cached releases, and configuration files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and repair installation problems for oh-my-claudecode, especially when legacy hooks, stale caches, outdated configuration, or duplicated files are causing the setup to break.

Core Features & Use Cases

  • Installation Diagnostics: Checks plugin version state, cache contents, and configuration files to identify what is wrong.
  • Legacy Cleanup Detection: Finds old hooks, scripts, and curl-installed content that can conflict with the plugin-based setup.
  • Configuration Validation: Verifies CLAUDE.md and related companion files to confirm the expected OMC markers are present.
  • Use Case: A user reports that Claude Code is loading duplicate behaviors after an upgrade; this Skill traces the conflict sources and recommends the exact cleanup steps.

Quick Start

Ask the skill to inspect your oh-my-claudecode setup, report every installation issue it finds, and recommend the safest fixes.

Frequently Asked Questions about omc-doctor

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

FAQPage Schema
How do I diagnose oh-my-claudecode installation problems causing duplicate behaviors in Claude Code?

Diagnose oh-my-claudecode installation problems by checking plugin versions, legacy hooks, cached releases, and configuration files to identify outdated scripts or duplicate settings causing conflicts. The skill traces conflict sources and recommends exact cleanup steps.

Why does my Claude Code configuration break after an oh-my-claudecode upgrade?

Claude Code configuration breaks after an oh-my-claudecode upgrade when legacy hooks, stale plugin caches, or outdated curl-installed scripts conflict with the new plugin-based setup. This skill identifies these outdated elements and recommends safe removal.

What is the best way to clean up legacy oh-my-claudecode hooks and scripts?

The best way to clean up legacy oh-my-claudecode hooks and scripts is to validate local filesystem state and detect old curl-installed content without removing custom user content. This skill finds conflicting legacy files and recommends targeted fixes.

How do I validate CLAUDE.md configuration files for missing OMC markers?

Validate CLAUDE.md configuration files for missing OMC markers by verifying companion files to confirm expected plugin identifiers are present. This skill checks settings.json contents and configuration consistency to ensure proper oh-my-claudecode integration.

Can I repair a broken oh-my-claudecode setup without losing my custom configuration?

You can repair a broken oh-my-claudecode setup without losing custom configuration because this skill validates filesystem state, settings.json contents, and plugin cache consistency while explicitly preserving your custom user content throughout the diagnostic and repair process.

What causes duplicate plugin behaviors in Claude Code environments?

Duplicate plugin behaviors in Claude Code environments are caused by outdated scripts, duplicate settings.json entries, and legacy curl-installed content conflicting with plugin-based oh-my-claudecode setups. This skill diagnoses these specific conflict sources safely.