@sma1lboy/kobe 0.9.13 → 0.9.14

package/dist/skills/rove/SKILL.md

@@ -3,7 +3,7 @@ name: rove
 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.
 ---
 
-<!-- rove-skill-version: 34 — bump in lockstep with KOBE_SKILL_VERSION (src/lib/skill-install.ts). -->
+<!-- rove-skill-version: 35 — bump in lockstep with KOBE_SKILL_VERSION (src/lib/skill-install.ts). -->
 
 # Rove shell control
 
@@ -428,6 +428,18 @@ branch name — the spawner needs it to `land`. Use the BARE form: an explicit
 `--task-id <spawner>` skips dispatcher routing and lands on that task's
 canonical engine tab, which can be a different agent's session.
 
+**Name your branch before you report it.** A new task starts on an
+auto-generated placeholder branch (`new-task`, `duck`, …); you are the only
+party who knows what the work turned out to be. Once the shape is clear,
+rename it to a short descriptive name in this repo's own convention:
+
+```bash
+rove api set-branch --task-id "$ROVE_TASK_ID" --branch <descriptive-slug>
+```
+
+Do this while you work, not at the end — the branch name is what the user
+reads in the sidebar to tell your task from its siblings.
+
 **"Succeeded" means COMMITTED.** Green tests in your working tree are not a
 deliverable — the only thing `land` can merge is commits on your branch.
 Before reporting success: `git status` clean, your work committed with a

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "@sma1lboy/kobe",
-  "version": "0.9.13",
+  "version": "0.9.14",
   "description": "Rove — the agent multiplexer for your terminal. Run coding agents on parallel tasks with isolated worktrees and persistent sessions.",
   "keywords": [
     "terminal",