메뉴
Auto-detect and configure omo prerequisites — Stop hook registration, MCP settings, statusline configuration. Activate when #sw appears anywhere in the user message.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | setup-wizard |
| description | Auto-detect and configure omo prerequisites — Stop hook registration, MCP settings, statusline configuration. Activate when #sw appears anywhere in the user message. |
| argument-hint | [--full] |
| disable-model-invocation | false |
| allowed-tools | Read, Edit, Write, Glob, Grep, Bash, Task |
Configure omo for this workspace. Arguments: $ARGUMENTS
Phase 1 — Environment check:
hooks/hooks.json exists (plugin-native hooks). If present, hooks are auto-registered.bash scripts/ensure-hooks.sh to verify the ralph-loop Stop hook is registered. If the script registers the hook, report it. If it was already present, confirm.bash scripts/mcp-doctor.sh to check MCP configuration status..claude/state/ directory exists and is writable..omo/config.json exists. If not, note it for Phase 2.teams.enabled in .omo/config.json and CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS env var.Phase 2 — Auto-fix:
For each issue found in Phase 1:
ensure-hooks.sh already handled it..claude/state/ directory → create it with tasks/ and handoffs/ subdirectories.examples/..omo/config.json → run bash scripts/init-config.sh to generate default config.Phase 3 — Report:
Summarize in a table:
| Component | Status | Action taken |
|---|
Components to check:
Phase 4 — Full mode (if --full flag is present):
If the user passed --full:
/omo:repo-radar to generate a repository map..claude/state/task-history.log if it does not exist.bash scripts/new-task-note.sh "Initial setup complete".Tips:
Review the current diff, run the narrowest useful verification, and summarize remaining release risk. Activate when #sc appears anywhere in the user message.
Show unified omo status dashboard — boulder, ralph-loop, tasks, teams, and memory state at a glance. Activate when #ss appears anywhere in the user message.
Check if README.md and user guide reflect current project state — philosophy, features, agent models, skill list. Fix any drift. Activate when #sync appears anywhere in the user message.
Full release pipeline — commit, push, tag, GitHub release, marketplace version sync. Activate when #rel appears anywhere in the user message.
Triage a failure by capturing symptoms, narrowing reproduction, isolating likely files, and choosing the smallest useful verification loop. Activate when #bh appears anywhere in the user message.
Multi-perspective code review on the current diff or specified files. Examines correctness, security, performance, maintainability, and scope creep. Activate when #dr appears anywhere in the user message.