Use first for install/update routing — sends setup, doctor, or MCP requests to the correct OMC setup flow
79
—
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Use /oh-my-claudecode:setup as the unified setup/configuration entrypoint.
/oh-my-claudecode:setup # full setup wizard
/oh-my-claudecode:setup doctor # installation diagnostics
/oh-my-claudecode:setup mcp # MCP server configuration
/oh-my-claudecode:setup wizard --local # explicit wizard pathProcess the request by the first argument only so install/setup questions land on the right flow immediately:
wizard, local, global, or --force -> route to /oh-my-claudecode:omc-setup with the same remaining argsdoctor -> route to /oh-my-claudecode:omc-doctor with everything after the doctor tokenmcp -> route to /oh-my-claudecode:mcp-setup with everything after the mcp tokenExamples:
/oh-my-claudecode:setup --local # => /oh-my-claudecode:omc-setup --local
/oh-my-claudecode:setup doctor --json # => /oh-my-claudecode:omc-doctor --json
/oh-my-claudecode:setup mcp github # => /oh-my-claudecode:mcp-setup github/oh-my-claudecode:omc-setup, /oh-my-claudecode:omc-doctor, and /oh-my-claudecode:mcp-setup remain valid compatibility entrypoints./oh-my-claudecode:setup in new documentation and user guidance.Task: {{ARGUMENTS}}
6c59219
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.