You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4907144
Browse filesBrowse the repository at this point in the historyBrowse files
fix(agent): align worker tool names and skills with the consolidated fleet
The worker prompt listed write, edit and delete on gpt while the wire
carries apply_patch; it now lists what the wire carries. Skills that told
agents to spawn builder, critic, intern or greybeard point at coder,
reviewer and planner, and stale director names in comments are gone.
|`--provider <name>` / `--model <id>`| Required unless `--matrix`. Single-variant via `loadConfig`. Not inferred from local settings |
190
-
|`--matrix <cells>`| Alternative to `--provider`/`--model`. Multi-variant: `p:m,p2:m2` or `label=p:m` (comma-separated). Every cell must include both sides |
|`--repeats <n>`| Runs per case×variant cell (default `1`; gate runs use `5`, baseline freezes `3`). Results record every repeat plus per-cell aggregates |
198
-
|`--concurrency <n>`| Independent case×variant×repeat cells in parallel (default `1`, env `CORBITS_EVAL_CONCURRENCY`). Each cell still uses its own temp workdir. Use `--concurrency 4` (or similar) to run a live matrix faster |
199
-
|`--dry-run`| Load cases × variants and print plan; no inference. Still requires `--provider`/`--model` or `--matrix`|
200
-
|`--director <id>`| Exec overlay: run the product `corbits exec` path with this director's system prompt and initially-advertised tool set (default: skywalker). Eval/CI override, not single-agent mode. Directors that cannot spawn (for example `build`) do not mount `spawn_agent` / `wait_agents`. |
|`--provider <name>` / `--model <id>`| Required unless `--matrix`. Single-variant via `loadConfig`. Not inferred from local settings |
190
+
|`--matrix <cells>`| Alternative to `--provider`/`--model`. Multi-variant: `p:m,p2:m2` or `label=p:m` (comma-separated). Every cell must include both sides |
|`--repeats <n>`| Runs per case×variant cell (default `1`; gate runs use `5`, baseline freezes `3`). Results record every repeat plus per-cell aggregates |
198
+
|`--concurrency <n>`| Independent case×variant×repeat cells in parallel (default `1`, env `CORBITS_EVAL_CONCURRENCY`). Each cell still uses its own temp workdir. Use `--concurrency 4` (or similar) to run a live matrix faster |
199
+
|`--dry-run`| Load cases × variants and print plan; no inference. Still requires `--provider`/`--model` or `--matrix`|
200
+
|`--director <id>`| Exec overlay: run the product `corbits exec` path with this director's system prompt and initially-advertised tool set (default: dispatch). Eval/CI override, not single-agent mode. Directors that cannot spawn (for example `build`) do not mount `spawn_agent` / `wait_agents`. |
Copy file name to clipboardExpand all lines: plugins/corbits-skills/skills/git-worktrees/SKILL.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ description: Create a git worktree from origin/<default-branch> and tear it down
7
7
8
8
# git-worktrees
9
9
10
-
How to create a worktree from origin/<default-branch> and tear it down. Load via `use_skill("git-worktrees")` and copy commands into an intern brief. Intern executes via `run_shell`. Do not run the git on the parent.
10
+
How to create a worktree from origin/<default-branch> and tear it down. Load via `use_skill("git-worktrees")` and copy commands into a coder brief. The coder executes via `run_shell`. Do not run the git on the parent.
Always base new branches on `origin/<default-branch>` (whatever the repository uses). After creating the worktree, intern`cd`s into it and installs local dependencies (`bun install` when the project uses Bun; otherwise follow developer docs). Worktrees do not share `node_modules`.
20
+
Always base new branches on `origin/<default-branch>` (whatever the repository uses). After creating the worktree, the coder`cd`s into it and installs local dependencies (`bun install` when the project uses Bun; otherwise follow developer docs). Worktrees do not share `node_modules`.
GaaS scribe uses the `question` tool. Corbits extras: `ask_operator` (tool mapping above). Do not fork the GaaS scribe body.
51
51
52
-
When GaaS implement says you are orchestrated by karen, that is the Corbits primary (Skywalker). Route those disposition decisions through the primary, not a worker.
52
+
When GaaS implement says you are orchestrated by karen, that is the Corbits primary (Dispatch). Route those disposition decisions through the primary, not a worker.
53
53
54
-
GaaS implement "Initial Planning" / Greybeard-before-code is not `/plan`. Substantial Builder work consumes a counsel / `/plan` plan (files, acceptance criteria, non-goals, risks, ordered steps) and blocks if that plan is missing. Tiny parent-DIY stays plan-optional. `/plan` and counsel author; they do not ship. `/implement` does not steal planning from `/plan`. Do not fork the GaaS implement body.
54
+
GaaS implement "Initial Planning" / Greybeard-before-code is not `/plan`. Substantial coder work consumes a planner / `/plan` plan (files, acceptance criteria, non-goals, risks, ordered steps) and blocks if that plan is missing. Tiny parent-DIY stays plan-optional. `/plan` and planner author; they do not ship. `/implement` does not steal planning from `/plan`. Do not fork the GaaS implement body.
55
55
56
56
## Linear claim-first
57
57
@@ -67,7 +67,7 @@ GaaS linear-issue-workflow inlines `git worktree add` and marks In Progress afte
67
67
68
68
GaaS `style` refuses to operate outside a git repo. Corbits does not: a folder without `.git` is a valid working directory (scratch, unpacked tarball, new project). Git-using skills (`implement`, `review`, `git-rebase`, `pull-request-review`) still no-op or ask when they need a repo. Do not invent a git repo to satisfy those skills.
69
69
70
-
When GaaS git-rebase writes `/tmp` editor scripts, Corbits still plans on the primary and intern executes sequenced git via `bash`; intern may use inline `GIT_SEQUENCE_EDITOR` instead of write editor scripts. Do not fork the GaaS git-rebase body.
70
+
When GaaS git-rebase writes `/tmp` editor scripts, Corbits still plans on the primary and the coder executes sequenced git via `bash`; it may use inline `GIT_SEQUENCE_EDITOR` instead of write editor scripts. Do not fork the GaaS git-rebase body.
71
71
72
72
## Tracker-agnostic issues
73
73
@@ -100,14 +100,14 @@ Do **not** post when the user only asked for a private/local read with no PR, or
100
100
101
101
### Multi-persona reviews
102
102
103
-
When the workflow ran more than one review lens (for example `critic` for behavioral/architecture, `greybeard` for waivers or product judgment, an OSS/quality agent for packaging and public-API bar), each lens that produced a distinct judgment **posts its own review**. Do not collapse independent verdicts into one mushy "team thinks" paragraph.
103
+
When the workflow ran more than one review lens (for example `reviewer` for behavioral/architecture, `planner` for waivers or product judgment, an OSS/quality agent for packaging and public-API bar), each lens that produced a distinct judgment **posts its own review**. Do not collapse independent verdicts into one mushy "team thinks" paragraph.
| Primary / orchestrator | Verdict on the branch as it stands; residual findings; waiver list | Always when posting |
108
+
|Reviewer| Behavioral bugs, missing tests, architecture, commit coherence | When a reviewer director ran |
109
+
|Planner| Waiver rulings and intentional exceptions | When the planner authorized any waiver, or when product/architecture judgment was requested |
110
+
| OSS / quality | Public-API, packaging, polish bar for shippable surface | When that lens was explicitly run |
111
111
112
112
Same GitHub account is fine. Label each post so a human can tell which lens spoke. Prefer separate `gh pr review` / `gh pr comment` posts over one mega-comment when more than one lens has substance.
0 commit comments