Controls Rove tasks, parallel coding agents, and worktree lifecycles through the rove api CLI.
npx skills add https://github.com/Sma1lboy/rove --skill rove-sma1lboy
Please help me install this Agent Skill. Skill: rove Source: https://github.com/Sma1lboy/rove/tree/main/claude-plugin/skills/rove Command: npx skills add https://github.com/Sma1lboy/rove --skill rove-sma1lboy
rove api CLI so every piece of delegated work gets its own git worktree, branch, tracked lifecycle, and a reliable messaging channel between agent sessions. ## Core Features & Use Cases - Task routing and creation: Maps user intent ("try it 3 ways", "in this workspace", "let codex take over") to the right verb — add for new isolated tasks, send --tab new for a helper in the same checkout, pane-open for splits. - Parallel attempts and comparison: add --count N or --agents claude:2,codex:1 spawns parallel attempts; collect --group gathers their outcomes for comparison. - Peer messaging between agent sessions: send is the only sanctioned channel for agent-to-agent messages, with [ROVE PEER] provenance prefixes and tab-precise reply addressing. - Lifecycle and issue tracking: rename, set-branch, land (merge), delete tasks, plus a daemon-owned kanban issue tracker and cron-style routines. - Use Case: Inside a Rove session, a user says "try three approaches to the caching bug and compare them" — the agent runs rove api add --repo "$PWD" --count 3 --prompt "...", then rove api collect --group <groupId> to report the outcomes. ## Quick Start Ask the agent to check whether $ROVE_TASK_ID is set and then use rove api to create, message, or collect Rove tasks for the work you describe.High-intent search queries and answers about installing and using this skill.
Use rove api add with --count N for identical parallel attempts or --agents claude:2,codex:1 to mix engines. Each attempt gets its own git worktree and branch, and rove api collect --group <groupId> gathers all outcomes for comparison.
Use rove api send --task-id <id> --tab tab-N --prompt "..." with the tab id from get-task's .tabs[] list. Inside a Rove task, send automatically prefixes messages with [ROVE PEER] provenance including a tab-precise reply command.
A task owns an isolated git worktree and branch. A terminal tab is a separate engine session sharing the same task files. A split only divides one tab's screen layout and isolates nothing, so parallel work requires new tasks, not tabs or splits.
Rove refuses a succeeded: report from a managed task whose branch has zero commits, because only committed work can be merged by land. Commit your changes first, or pass --allow-empty when the task legitimately produced no commits, such as an investigation.
Yes, rove api routine-create takes a five-field cron schedule, a repo, and a prompt. Each firing creates a fresh task by default, or reuses one standing conversation with --persistent-session, and --precheck skips runs when there is nothing to do.
Do not create a task when the user asks you to do the work directly, when a helper should share your current checkout (use send --tab new instead), or for small reversible changes. Also never recursively fan out new tasks from a spawned task.
supercent-ioReview AI agent plans and git diffs through a visual browser UI.
codetail-aiReview pull request diffs for correctness, safety, and boundary issues.
swarm-ai-researchMonitors on-chain DeFi positions and liquidity pools for health, yield, and risk events.
Zidane786Orchestrate parallel Codex CLI agents in isolated git worktrees and tmux sessions.