kocao

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.

Use when creating and writing an Ito change proposal (new change or existing change id). Delegates to Ito CLI instruction artifacts.

Use when executing implementation plans with independent tasks in the current session using subagents

Use Ito tasks CLI to manage tasks.md (status/next/start/complete/shelve/add).

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use before claiming work is complete, finished, fixed, or passing — requires running verification commands and confirming output before making success claims

Ito workflow delegation - delegates all workflow content to Ito CLI instruction artifacts.

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.

Archive a completed change and update main specifications. Use when the user has finished implementing and wants to integrate the change into the main codebase.

Create atomic git commits aligned to Ito changes. Use when you want to commit work after applying a change, optionally with auto-mode.

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

List Ito changes, specs, or modules with status summaries and intelligent interpretation.

Use when you need stable absolute paths (project/worktree/.ito/worktrees) without embedding machine-specific paths into committed files

Conduct structured research for feature development, technology evaluation, or problem investigation. Use when the user needs to explore options, analyze trade-offs, or investigate technical approaches.

Review and validate Ito changes, specs, or implementations. Use when the user wants a quality check, code review, or validation of project artifacts.

Unified entry point for ito commands with intelligent skill-first routing and CLI fallback.

Use when tests need to be run with minimal output noise and delegated execution; routes test runs through the dedicated test-runner subagent and returns curated pass/fail evidence.

Use when discovering, finding, invoking, or loading skills. Ensures skills are invoked BEFORE responding.

Use when creating, designing, planning, proposing, or specifying a feature, change, requirement, enhancement, fix, modification, or spec. Use when writing tasks, proposals, specifications, or requirements for new work.