Menu
List Ito changes, specs, or modules with status summaries and intelligent interpretation.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Manage remote Kocao agent sessions from an AI assistant. Use when: listing running agents, starting a new remote agent, checking agent status, viewing agent logs, stopping an agent session, or sending a prompt to a running remote agent.
Fast trigram-indexed code search across the entire repository using Zoekt (the engine behind GitHub and Sourcegraph code search). Use INSTEAD OF grep/ripgrep for broad codebase searches. Supports regex, literal strings, file filters, and symbol queries. Auto-installs zoekt binaries and auto-indexes the repo on first use.
Apply a Change Proposal. Triggered by the user saying "Apply change <change-id>" or "Implement change <change-id>". Use when implementing, executing, applying, building, coding, or developing a feature, change, requirement, enhancement, fix, or modification. Use when running tasks from a spec, proposal, or plan.
You MUST use this before any creative work - creating features, proposing changes,building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — presents structured options for merge, PR, or cleanup
Run an ito ralph loop for a specific change (or module/repo sequence), with safe defaults and automatic restart context on early exits.
| name | ito-list |
| description | List Ito changes, specs, or modules with status summaries and intelligent interpretation. |
Use ito list to display project items and interpret the results for the user.
Goal
Run the appropriate ito list command, present the output clearly, and offer
context-aware suggestions based on the results (e.g., which changes are ready
for implementation, which are partially complete, or what to work on next).
CLI Reference
ito list [OPTIONS]
Item types (default: changes):
--changes List changes (default)
--specs List specs
--modules List modules
Progress filters (changes only, mutually exclusive):
--ready Changes ready for implementation (have proposal, specs, tasks, and pending work)
--completed Changes with all tasks done
--partial Changes with some but not all tasks done
--pending Changes with no tasks started
Other options:
--sort <ORDER> Sort order: recent (default) or name
--json Output as JSON
Steps
Parse user intent from the arguments:
--json for structured output that is easier to interpret programmaticallyRun the CLI command:
ito list invocationito list --ready --json or ito list --specsPresent and interpret results:
ito list --partial to see in-progress work.")Suggest next actions based on the results:
/ito-apply <change-id> to start implementing/ito-apply <change-id>/ito-archive <change-id>ito create changeExamples
# List all changes (default)
ito list
# List only changes ready for implementation
ito list --ready
# List specs
ito list --specs
# List changes with JSON output for analysis
ito list --json
# List completed changes (candidates for archiving)
ito list --completed
# List modules
ito list --modules
Guardrails
--json when you need to programmatically interpret results.--ready, --completed, --partial, --pending) only apply to changes, not specs or modules.ito init.