omc-doctor

Diagnose and fix oh-my-claudecode installation issues across Claude configurations.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/INNERJOINT/HarnessSkills --skill omc-doctor-innerjoint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omc-doctor
Source: https://github.com/INNERJOINT/HarnessSkills/tree/main/skills/omc-doctor
Command: npx skills add https://github.com/INNERJOINT/HarnessSkills --skill omc-doctor-innerjoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The OMC Doctor automates detection and remediation of common oh-my-claudecode (OMC) installation and configuration problems that cause duplicate hooks, stale plugin caches, missing CLAUDE.md configuration, and legacy curl-installed artifacts.

Core Features & Use Cases

  • Plugin version checks: Detects installed versus latest plugin versions and warns about multiple cached versions.
  • Legacy hook and script detection: Scans profile and project settings for legacy "hooks" entries and common bash hook scripts that can cause duplicate behavior.
  • CLAUDE.md validation: Verifies the presence and OMC markers in CLAUDE.md and companion files, and can fetch the canonical CLAUDE.md when missing or outdated.
  • Legacy curl-installed content audit: Identifies legacy agents, commands, and skills that were installed before the plugin system and recommends safe cleanup with user confirmation.
  • Auto-fix workflow: Offers optional, reversible fixes (backup-first recommended) including removing legacy hooks/scripts, clearing plugin cache, and fetching updated CLAUDE.md.

Quick Start

Run the OMC Doctor to scan your home and project Claude configuration and confirm any recommended 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 issues and duplicate hooks?

Diagnosing oh-my-claudecode installation issues involves scanning your ~/.claude and project ./.claude directories to detect legacy hooks, stale plugin caches, and missing CLAUDE.md markers. The OMC Doctor automates this detection process across user and project configurations to pinpoint duplicate behavior and configuration drift.

What is the best way to clean up legacy curl-installed Claude agents and commands?

Cleaning up legacy curl-installed Claude agents and commands requires auditing your configuration directories for artifacts installed before the plugin system. The OMC Doctor identifies these legacy files and offers optional, reversible removal workflows with user confirmation to ensure safe cleanup.

Why does my Claude plugin configuration have stale caches and missing CLAUDE.md markers?

Stale plugin caches and missing CLAUDE.md markers happen when oh-my-claudecode installations are not updated cleanly or legacy configurations override current plugin settings. The OMC Doctor checks plugin cache contents and validates CLAUDE.md companion files to identify these configuration inconsistencies.

Can I automatically fetch the canonical CLAUDE.md from GitHub to fix missing configuration?

Yes, you can fetch the canonical CLAUDE.md from GitHub to fix missing configuration. The OMC Doctor's auto-fix workflow requests optional permission to retrieve the canonical CLAUDE.md file from GitHub when it detects missing OMC markers or outdated configuration during its validation scan.

Does the OMC Doctor require write access to remove legacy hook scripts from Claude settings?

The OMC Doctor requires read access to your ~/.claude and project ./.claude directories for scanning legacy hook scripts, plus optional permission to remove or update legacy files. It scans profile and project settings for legacy hooks entries and offers reversible fixes with backup-first recommendations.