@sma1lboy/kobe 0.8.52 → 0.8.55
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 +421 -421
- package/dist/skills/kobe/SKILL.md +32 -1
- package/package.json +1 -1
|
@@ -3,7 +3,7 @@ name: kobe
|
|
|
3
3
|
description: Use when controlling kobe tasks, parallel coding attempts, hosted agent sessions, task lifecycle, or the daemon-owned issue tracker from a shell.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
<!-- kobe-skill-version:
|
|
6
|
+
<!-- kobe-skill-version: 7 — bump in lockstep with KOBE_SKILL_VERSION (src/lib/skill-install.ts). -->
|
|
7
7
|
|
|
8
8
|
# kobe shell control
|
|
9
9
|
|
|
@@ -11,6 +11,37 @@ Use `kobe api` to manage local coding tasks. Each Task owns a git Worktree,
|
|
|
11
11
|
branch, and Hosted PTY engine sessions. API automation works without an open
|
|
12
12
|
TUI; prompted `send`, `add`, and `fan-out` ensure the canonical engine session.
|
|
13
13
|
|
|
14
|
+
## Inside a kobe session, kobe verbs come first
|
|
15
|
+
|
|
16
|
+
Check where you are before choosing how to delegate or parallelize:
|
|
17
|
+
|
|
18
|
+
```bash
|
|
19
|
+
test -n "${KOBE_TASK_ID:-}"
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
When that passes, you are an engine session kobe manages — `$KOBE_TASK_ID`
|
|
23
|
+
is your task, `$KOBE_TAB_ID` your tab. Coordination should then go through
|
|
24
|
+
kobe, not around it, because work routed through `kobe api` gets what
|
|
25
|
+
ad-hoc subprocesses never do: its own Worktree and branch (no file
|
|
26
|
+
collisions with you), a sidebar row with live state the user can watch,
|
|
27
|
+
lifecycle tracking, and an explicit outcome contract.
|
|
28
|
+
|
|
29
|
+
- Parallel attempts of one prompt → `fan-out`, not N hand-rolled subagents.
|
|
30
|
+
- Delegating a scoped piece of work → `add --prompt`, not a raw `claude -p`
|
|
31
|
+
child the user cannot see or manage.
|
|
32
|
+
- Following up on a task you started → `send`; waiting on results →
|
|
33
|
+
`await`; comparing → `collect`; reporting your own verdict → `report`.
|
|
34
|
+
- Messaging another live session → `dispatch` (never impersonate the user
|
|
35
|
+
in someone else's terminal).
|
|
36
|
+
|
|
37
|
+
Your own engine's in-context subagents remain fine for read-only
|
|
38
|
+
research/exploration inside your task — the boundary is WORK: anything that
|
|
39
|
+
edits files, runs long, or the user should be able to see and steer belongs
|
|
40
|
+
in a kobe task. Do not recursively fan out from a spawned task.
|
|
41
|
+
|
|
42
|
+
When the check fails, none of this applies — use `kobe api` only if the
|
|
43
|
+
user asks for kobe by name.
|
|
44
|
+
|
|
14
45
|
## Discover before calling
|
|
15
46
|
|
|
16
47
|
```bash
|
package/package.json
CHANGED