@sma1lboy/kobe 0.9.26 → 0.9.28
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cli/index.js +334 -334
- package/dist/cli/kobe-run.js +318 -318
- package/dist/cli/rove-run.js +318 -318
- package/dist/skills/rove/SKILL.md +23 -1
- package/package.json +1 -1
|
@@ -3,7 +3,7 @@ name: rove
|
|
|
3
3
|
description: Use when controlling Rove tasks, parallel coding attempts, hosted agent sessions, task lifecycle, or the daemon-owned issue tracker from a shell. Also the ONLY channel for messaging another agent session on this machine — `rove api send`, never a peer/MCP side channel.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
<!-- rove-skill-version:
|
|
6
|
+
<!-- rove-skill-version: 37 — bump in lockstep with KOBE_SKILL_VERSION (src/lib/skill-install.ts). -->
|
|
7
7
|
|
|
8
8
|
# Rove shell control
|
|
9
9
|
|
|
@@ -457,6 +457,28 @@ real message (you wrote the code; you write its message). A worker that ran
|
|
|
457
457
|
everything, passed everything, and committed nothing has delivered nothing —
|
|
458
458
|
that exact mismatch has shipped empty merges before.
|
|
459
459
|
|
|
460
|
+
Rove now checks this at the moment you claim it: a `succeeded:` report from a
|
|
461
|
+
managed task whose branch has **0 commits** is refused with
|
|
462
|
+
`EMPTY_SUCCESS_REPORT` and never reaches the coordinator. Commit, then send.
|
|
463
|
+
When the task genuinely produced no commits — an investigation, a review, a
|
|
464
|
+
question answered — say so explicitly with `--allow-empty`:
|
|
465
|
+
|
|
466
|
+
```bash
|
|
467
|
+
rove api send --allow-empty --prompt "succeeded: no bug — root cause is upstream, see notes"
|
|
468
|
+
```
|
|
469
|
+
|
|
470
|
+
**"CI is green" means `checkState: passing`.** A local test run is not CI: it
|
|
471
|
+
does not run the other jobs, the other platform, or the merge gates. Rove
|
|
472
|
+
polls your PR's checks and keeps the answer on the task —
|
|
473
|
+
|
|
474
|
+
```bash
|
|
475
|
+
rove api get-task --task-id "$ROVE_TASK_ID" # .task.prStatus.checkState
|
|
476
|
+
```
|
|
477
|
+
|
|
478
|
+
`none` (no PR yet) / `pending` (still running) / `passing` / `failing` /
|
|
479
|
+
`unknown`. Anything but `passing` is not green. Report what the field says,
|
|
480
|
+
not what your local run implied.
|
|
481
|
+
|
|
460
482
|
**Coordinator side** — do NOT block or poll. Keep working (or end your
|
|
461
483
|
turn); each worker's outcome arrives in your chat as a `[ROVE PEER]` message
|
|
462
484
|
with its task id. What arrives is the worker's claim, not Rove-verified —
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"$schema": "https://json.schemastore.org/package.json",
|
|
3
3
|
"name": "@sma1lboy/kobe",
|
|
4
|
-
"version": "0.9.
|
|
4
|
+
"version": "0.9.28",
|
|
5
5
|
"description": "Rove — the agent multiplexer for your terminal. Run coding agents on parallel tasks with isolated worktrees and persistent sessions.",
|
|
6
6
|
"keywords": [
|
|
7
7
|
"terminal",
|