원클릭으로
ito-loop
Run an ito ralph loop for a change, module, or repo-ready sequence, with safe defaults and automatic restart context on early exits.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Run an ito ralph loop for a change, module, or repo-ready sequence, with safe defaults and automatic restart context on early exits.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Build reproducible Showboat demo documents that prove repo behavior with executable markdown. Use when asked to create demos, proof-of-work walkthroughs, or verification artifacts with showboat, especially for tests, CLIs, local services, Aspire AppHosts, and HTTP APIs.
Build reproducible Showboat demo documents that prove repo behavior with executable markdown. Use when asked to create demos, proof-of-work walkthroughs, or verification artifacts with showboat, especially for tests, CLIs, local services, Aspire AppHosts, and HTTP APIs.
Balanced skill for typical development tasks, code review, and implementation work
Coordinator-only agent for orchestrating multi-change runs
Fast, cost-effective skill for simple tasks, quick queries, and small code changes
Read-only researcher for Ito orchestration context gathering
| name | ito-loop |
| description | Run an ito ralph loop for a change, module, or repo-ready sequence, with safe defaults and automatic restart context on early exits. |
Run ito ralph for one change, one module, or the next ready work item, with safe defaults and bounded restarts.
Parse /ito-loop arguments into one of these modes:
| Input | Mode | Command shape |
|---|---|---|
^[0-9]{3}-[0-9]{2}_[a-z0-9-]+$ | change | ito ralph ... --change <id> |
^[0-9]{3}$ | module | ito ralph ... --module <id> |
next, continue, natural language for next ready work, or empty | continue-ready | ito ralph ... --continue-ready |
--model <model-id>--max-iterations <n>--timeout <duration> (e.g. 15m)opencode, claude, codex, copilot, or pi)Parse input with ito util parse-id $ARGUMENTS:
parsed=$(ito util parse-id $ARGUMENTS)
mode=$(echo "$parsed" | jq -r '.mode')
id=$(echo "$parsed" | jq -r '.id // empty')
mode will be change, module, or continue-ready.id is set for change and module modes; empty for continue-ready.eval, and always quote variables.Choose the active harness.
Build one base ito ralph command. Ralph already manages its own internal loop, so do not wrap it in an unbounded retry loop.
Command shapes:
# Mode: change
ito ralph --no-interactive --harness <harness> --change <change-id> --max-iterations 5 --timeout 15m
# Mode: module
ito ralph --no-interactive --harness <harness> --module <module-id> --max-iterations 5 --timeout 15m
# Mode: continue-ready
ito ralph --no-interactive --harness <harness> --continue-ready --max-iterations 5 --timeout 15m
Apply any user-provided overrides on top of the defaults. Check ito ralph --help only if extra flags matter.
Run the command once.
0: report success and stop.For each bounded restart, collect context from:
ito ralph --no-interactive --change <change-id> --status
ito tasks status <change-id>
Summarize the context into a short restart note containing:
You have been restarted ...Append it before the rerun:
ito ralph --no-interactive --change <change-id> --add-context "<restart-note>"
Re-run the same base command.
After the supervised run sequence finishes:
ito ralph --status and ito tasks status are meaningful.