Catalog
Yeachan-Heo/omc-setup

Yeachan-Heo

omc-setup

Install or refresh oh-my-claudecode for plugin, npm, and local-dev setups from the canonical setup flow

global
0installs0uses~1.9k
v1.1Saved Apr 20, 2026

OMC Setup

This is the only command you need to learn. After running this, everything else is automatic.

When this skill is invoked, immediately execute the workflow below. Do not only restate or summarize these instructions back to the user.

Note: All ~/.claude/... paths in this guide respect CLAUDE_CONFIG_DIR when that environment variable is set.

Best-Fit Use

Choose this setup flow when the user wants to install, refresh, or repair OMC itself.

  • Marketplace/plugin install users should land here after /plugin install oh-my-claudecode
  • npm users should land here after npm i -g oh-my-claude-sisyphus@latest
  • local-dev and worktree users should land here after updating the checked-out repo and rerunning setup

Flag Parsing

Check for flags in the user's invocation:

  • --help → Show Help Text (below) and stop
  • --local → Phase 1 only (target=local), then stop
  • --global → Phase 1 only (target=global), then stop
  • --force → Skip Pre-Setup Check, run full setup (Phase 1 → 2 → 3 → 4)
  • No flags → Run Pre-Setup Check, then full setup if needed

Help Text

When user runs with --help, display this and stop:

OMC Setup - Configure oh-my-claudecode

USAGE:
  /oh-my-claudecode:omc-setup           Run initial setup wizard (or update if already configured)
  /oh-my-claudecode:omc-setup --local   Configure local project (.claude/CLAUDE.md)
  /oh-my-claudecode:omc-setup --global  Configure global settings (~/.claude/CLAUDE.md)
  /oh-my-claudecode:omc-setup --force   Force full setup wizard even if already configured
  /oh-my-claudecode:omc-setup --help    Show this help

MODES:
  Initial Setup (no flags)
    - Interactive wizard for first-time setup
    - Configures CLAUDE.md (local or global)
    - Sets up HUD statusline
    - Checks for updates
    - Offers MCP server configuration
    - Configures team mode defaults (agent count, type, model)
    - If already configured, offers quick update option

  Local Configuration (--local)
    - Downloads fresh CLAUDE.md to ./.claude/
    - Backs up existing CLAUDE.md to .claude/CLAUDE.md.backup.YYYY-MM-DD
    - Project-specific settings
    - Use this to update project config after OMC upgrades

  Global Configuration (--global)
    - Downloads fresh CLAUDE.md to ~/.claude/
    - Backs up existing CLAUDE.md to ~/.claude/CLAUDE.md.backup.YYYY-MM-DD
    - Default: explicitly overwrites ~/.claude/CLAUDE.md so plain `claude` also uses OMC
    - Optional preserve mode keeps the user's base `CLAUDE.md` and installs OMC into `CLAUDE-omc.md` for `omc` launches
    - Applies to all Claude Code sessions
    - Cleans up legacy hooks
    - Use this to update global config after OMC upgrades

  Force Full Setup (--force)
    - Bypasses the "already configured" check
    - Runs the complete setup wizard from scratch
    - Use when you want to reconfigure preferences

EXAMPLES:
  /oh-my-claudecode:omc-setup           # First time setup (or update CLAUDE.md if configured)
  /oh-my-claudecode:omc-setup --local   # Update this project
  /oh-my-claudecode:omc-setup --global  # Update all projects
  /oh-my-claudecode:omc-setup --force   # Re-run full setup wizard

For more info: https://github.com/Yeachan-Heo/oh-my-claudecode

Pre-Setup Check: Already Configured?

CRITICAL: Before doing anything else, check if setup has already been completed. This prevents users from having to re-run the full setup wizard after every update.

# Check if setup was already completed
CONFIG_FILE="${CLAUDE_CONFIG_DIR:-$HOME/.claude}/.omc-config.json"

if [ -f "$CONFIG_FILE" ]; then
  SETUP_COMPLETED=$(jq -r '.setupCompleted // empty' "$CONFIG_FILE" 2>/dev/null)
  SETUP_VERSION=$(jq -r '.setupVersion // empty' "$CONFIG_FILE" 2>/dev/null)

  if [ -n "$SETUP_COMPLETED" ] && [ "$SETUP_COMPLETED" != "null" ]; then
    echo "OMC setup was already completed on: $SETUP_COMPLETED"
    [ -n "$SETUP_VERSION" ] && echo "Setup version: $SETUP_VERSION"
    ALREADY_CONFIGURED="true"
  fi
fi

If Already Configured (and no --force flag)

If ALREADY_CONFIGURED is true AND the user did NOT pass --force, --local, or --global flags:

Use AskUserQuestion to prompt:

Question: "OMC is already configured. What would you like to do?"

Options:

  1. Update CLAUDE.md only - Download latest CLAUDE.md without re-running full setup
  2. Run full setup again - Go through the complete setup wizard
  3. Cancel - Exit without changes

If user chooses "Update CLAUDE.md only":

  • Detect if local (.claude/CLAUDE.md) or global (~/.claude/CLAUDE.md) config exists
  • If local exists, run: bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup-claude-md.sh" local
  • If only global exists, run: bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup-claude-md.sh" global
  • Skip all other steps
  • Report success and exit

If user chooses "Run full setup again":

  • Continue with Resume Detection below

If user chooses "Cancel":

  • Exit without any changes

Force Flag Override

If user passes --force flag, skip this check and proceed directly to setup.

Resume Detection

Before starting any phase, check for existing state:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup-progress.sh" resume

If state exists (output is not "fresh"), use AskUserQuestion to prompt:

Question: "Found a previous setup session. Would you like to resume or start fresh?"

Options:

  1. Resume from step $LAST_STEP - Continue where you left off
  2. Start fresh - Begin from the beginning (clears saved state)

If user chooses "Start fresh":

bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup-progress.sh" clear

Phase Execution

For --local or --global flags:

Read the file at ${CLAUDE_PLUGIN_ROOT}/skills/omc-setup/phases/01-install-claude-md.md and follow its instructions. (The phase file handles early exit for flag mode.)

For full setup (default or --force):

Execute phases sequentially. For each phase, read the corresponding file and follow its instructions:

  1. Phase 1 - Install CLAUDE.md: Read ${CLAUDE_PLUGIN_ROOT}/skills/omc-setup/phases/01-install-claude-md.md and follow its instructions.

  2. Phase 2 - Environment Configuration: Read ${CLAUDE_PLUGIN_ROOT}/skills/omc-setup/phases/02-configure.md and follow its instructions. Phase 2 must delegate HUD/statusLine setup to the hud skill; do not generate or patch statusLine paths inline here.

  3. Phase 3 - Integration Setup: Read ${CLAUDE_PLUGIN_ROOT}/skills/omc-setup/phases/03-integrations.md and follow its instructions.

  4. Phase 4 - Completion: Read ${CLAUDE_PLUGIN_ROOT}/skills/omc-setup/phases/04-welcome.md and follow its instructions.

Graceful Interrupt Handling

IMPORTANT: This setup process saves progress after each phase via ${CLAUDE_PLUGIN_ROOT}/scripts/setup-progress.sh. If interrupted (Ctrl+C or connection loss), the setup can resume from where it left off.

Keeping Up to Date

After installing oh-my-claudecode updates (via npm or plugin update):

Automatic: Just run /oh-my-claudecode:omc-setup - it will detect you've already configured and offer a quick "Update CLAUDE.md only" option that skips the full wizard.

Manual options:

  • /oh-my-claudecode:omc-setup --local to update project config only
  • /oh-my-claudecode:omc-setup --global to update global config only
  • /oh-my-claudecode:omc-setup --force to re-run the full wizard (reconfigure preferences)

This ensures you have the newest features and agent configurations without the token cost of repeating the full setup.

Files5
5 files · 25.9 KB

Select a file to preview

Overall Score

78/100

Grade

B

Good

Safety

76

Quality

82

Clarity

75

Completeness

78

Summary

OMC Setup is an interactive installation and configuration skill for oh-my-claudecode, a Claude Code enhancement framework. It guides users through a multi-phase setup process covering CLAUDE.md installation, environment configuration (HUD, execution modes, CLI tools), MCP integration, and optional agent team setup. The skill manages state persistence to allow resumable interrupted setups.

Static Analysis Findings

2 findings

Patterns detected by deterministic static analysis before AI scoring. Hover over any finding code for detailed information and remediation guidance.

Credential Exposure
SEC-020Direct .env File Access5x in 2 files

Direct .env file access

phases/02-configure.md.env2x
phases/03-integrations.md.env3x
Destructive Operation
SEC-002Privilege Escalation

Privilege escalation (sudo)

phases/02-configure.mdsudo n

Detected Capabilities

Interactive user prompts via AskUserQuestionFile read/write operations on ~/.claude/ and ./.claude/ directoriesEnvironment variable detection and configurationJSON-based state management and persistenceGit repository detection and configurationnpm package detection and installationShell script delegation for canonical source handlingsettings.json manipulation for Claude Code configurationGitHub API interaction via gh CLIPhase-based resumable setup workflow

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

install oh-my-claudecodeOMC setupconfigure claudeupgrade oh-my-claudecoderepair omc installation

Risk Signals

WARNING

sudo npm install -g oh-my-claude-sisyphus (SEC-002)

phases/02-configure.md, Step 2.5
INFO

.env file access (SEC-020)

phases/02-configure.md (multiple mentions), phases/03-integrations.md (multiple mentions)
INFO

Recursive deletion via rm -rf in state management (implicit in setup-progress.sh clear command, SEC-001)

phases/01-install-claude.md, early exit for flag mode
INFO

Direct environment variable reading (CLAUDE_CONFIG_DIR, CLAUDE_PLUGIN_ROOT, npm PATH, etc.)

Throughout all phases
INFO

GitHub raw content download (https://raw.githubusercontent.com/...)

phases/01-install-claude-md.md, fallback instructions

Referenced Domains

External domains referenced in skill content, detected by static analysis.

code.claude.comgithub.comraw.githubusercontent.com

Use Cases

  • Install oh-my-claudecode for the first time
  • Update or refresh OMC configuration after upgrades
  • Configure project-specific or global Claude Code settings
  • Set up MCP servers and agent teams
  • Repair or reset an existing OMC installation

Quality Notes

  • ✓ STRENGTH: Excellent instruction structure with clear phase breakdown. Each phase is in a separate file and explicitly numbered, making resumability clear.
  • ✓ STRENGTH: Comprehensive state management documented — setup progress is saved after each phase, allowing graceful interruption recovery.
  • ✓ STRENGTH: Strong defensive design for pre-setup checks ('already configured' detection) reduces token waste and user friction.
  • ✓ STRENGTH: Multiple configuration branches (--local, --global, --force flags) are clearly explained with distinct code paths.
  • ✓ STRENGTH: Proper escalation path for user choices — uses AskUserQuestion for all interactive decisions, no hardcoded assumptions.
  • ✓ STRENGTH: Thorough error handling guidance, especially for fallback scenarios (npm not found, curl fails, etc.).
  • ✓ STRENGTH: Backward compatibility documented (upgrade path from 2.x, legacy hook cleanup mentioned).
  • ⚠ WEAKNESS: Phase files reference external scripts (setup-claude-md.sh, setup-progress.sh, hud skill) but the skill does not validate their existence or provide inline fallbacks. If scripts are missing, agent may fail without clear error message.
  • ⚠ WEAKNESS: Heavy reliance on jq for JSON manipulation — no fallback for systems without jq, though this is a minor edge case.
  • ⚠ WEAKNESS: The 'sudo npm' guidance in Step 2.5 is presented as acceptable for permission errors, but this is generally an anti-pattern. Documentation should emphasize fixing NODE_PATH or using nvm instead.
  • ⚠ WEAKNESS: settings.json modification uses jq directly without backup in some paths. Phase 3.3.1 mentions 'Edit tool is preferred' but then provides jq code — the relationship between Edit tool and jq code is unclear.
  • ✓ STRENGTH: Help text is comprehensive and well-formatted with examples and usage patterns.
  • ✓ STRENGTH: Integration with Claude Code native features (TeamCreate, TaskCreate, HUD) is properly delegated to specialized skills.
  • ⚠ WEAKNESS: Phase files contain inline bash code blocks that are presented as examples but lack clear 'execute vs. read' signaling in some cases. An agent might be confused about which blocks are pseudo-code templates vs. literal commands.
Model: claude-haiku-4-5-20251001Analyzed: Apr 20, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

v1.1

Content updated

2026-04-20

Latest
v1.0

No changelog

2026-04-12

Add Yeachan-Heo/omc-setup to your library

Command Palette

Search for a command to run...