Menu
Use when you need stable absolute paths (project/worktree/.ito/worktrees) without embedding machine-specific paths into committed files
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.
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.
Based on SOC occupation classification
| name | ito-path |
| description | Use when you need stable absolute paths (project/worktree/.ito/worktrees) without embedding machine-specific paths into committed files |
Use ito path ... to resolve filesystem paths at runtime.
This is the preferred way to:
# Stable root shared across worktrees
ito path project-root
# Current working worktree root (fails in bare repos)
ito path worktree-root
# Absolute path to the `.ito` directory
ito path ito-root
# Worktrees root (fails if worktrees disabled)
ito path worktrees-root
# A specific worktree directory
ito path worktree --main
ito path worktree --branch <name>
ito path worktree --change <change-id>
# Bundle of roots
ito path roots
ito path roots --json
project-root is stable across linked worktrees.worktree-root is the current working tree root.ito-root is the .ito directory for the current invocation.In a bare/control repo directory (no working tree), Ito should be run from a worktree. ito path worktree-root exits non-zero and prints a helpful error.
ito path project-root --json
Returns:
{ "path": "/abs/path" }
Committed files (templates/skills) should use repo-relative paths.
If an absolute path is needed at runtime (for agent output or scripts), instruct the caller to use ito path ....