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

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: Setup Invocation Do not independently scan plugin cache directories or select a plugin root in this skill. Invoke the setup script from the plugin root supplied by the running plugin environment: The script is the sole cache resolver. It accepts only complete plugin roots (canonical docs/CLAUDE.md , coordinator artifact, and wiki skill), chooses a strict full SemVer cache version, verifies the compiled source handshake, and fails closed on coordinator protocol or status disagreement. Do not download configuration or mutate CLAUDE.md outside that coordinator. 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. 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 and clear retired setup values Install the active plugin's canonical CLAUDE.md and run Phase 2 Step 2.4 without re running the full setup 2. Run full setup again Go through the complete setup wizard 3. Cancel Exit without changes If user chooses "Update CLAUDE.md and clear retired setup values": Detect if local (.claude/CLAUDE.md) or global (~/.claude/CLAUDE.md) config exists If local exists, run: bash "${OMC SETUP PLUGIN ROOT: ${CLAUDE PLUGIN ROOT}}/scripts/setup claude md.sh" local If only global exists, run: bash "${OMC SETUP PLUGIN ROOT: ${CLAUDE PLUGIN ROOT}}/scripts/setup claude md.sh" global Run Phase 2 Step 2.4 to clear the retired defaultExecutionMode key Skip all other steps after the cleanup 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: 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": Phase Execution For local or global flags: Read the file at ${OMC SETUP PLUGIN ROOT: ${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 ${OMC SETUP PLUGIN ROOT: ${CLAUDE PLUGIN ROOT}}/skills/omc setup/phases/01 install claude md.md and follow its instructions. 2. Phase 2 Environment Configuration : Read ${OMC SETUP PLUGIN ROOT: ${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 ${OMC SETUP PLUGIN ROOT: ${CLAUDE PLUGIN ROOT}}/skills/omc setup/phases/03 integrations.md and follow its instructions. 4. Phase 4 Completion : Read ${OMC SETUP PLUGIN ROOT: ${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 ${OMC SETUP PLUGIN ROOT: ${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 and clear retired setup values" option that skips the rest of the wizard. The quick update path must still perform Phase 2 Step 2.4 so upgrades remove the retired defaultExecutionMode value; it must not write any replacement execution mode setting. 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.

omc-setup