Menu
Review and validate Ito changes, specs, or implementations. Use when the user wants a quality check, code review, or validation of project artifacts.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | ito-review |
| description | Review and validate Ito changes, specs, or implementations. Use when the user wants a quality check, code review, or validation of project artifacts. |
Run the CLI-generated review instructions for a specific change.
This skill uses:
ito agent instruction review --change "<change-id>"
to generate a structured peer-review checklist before implementation.
Steps
Determine the target change ID (ask the user if unclear).
Generate instructions (source of truth):
ito agent instruction review --change "<change-id>"
Follow the printed instructions exactly.
Return findings using tags and verdict required by the instruction template:
[blocking], [suggestion], or [note].Verdict: approve, Verdict: request-changes, or Verdict: needs-discussion.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.