WB

Plugin wb from marketplace sneat-co in sneat-co/ai-marketplace. Commands read from the repo's manifest — 19 days ago.

Skills (21)

• move

  Transfer this whole WB session now: park it and start one successor here or on another machine. Use for /move, "move this session to the VM", "continue this session on Codex". Do not use for a bounded task delegated to a WB-dispatched worker (that is /offload) or to freeze without a successor (that

• offload

  Delegate a bounded coding task to a cheaper WB-dispatched worker agent, have a cheap native supervisor subagent manage and verify it, and get back one concise PASS / FAIL / ESCALATE verdict instead of the worker's transcript. Use for /offload, "offload this to a cheaper model", "hand this bounded ta

• park

  Freeze a WB agent session or a named task without starting a successor. Use for /park, "park this session", "checkpoint this work for later", or overnight stop. Do not use for in-harness subagents, or to start work on another machine now (that is /move or /offload), or to delegate a bounded task to

• pickup

  Start a successor for a previously parked WB session or task, locally or on another machine. Use for /pickup, "pick up parked work", "resume the parked session". Do not use for in-harness subagents, to freeze work (that is /park), or to delegate a bounded task to a WB-dispatched worker (that is /off

• wb-agents

  Use WB to dispatch, track, and inspect bounded coding work handed to a configured agent harness running inside an isolated WB worktree. Use for "offload this task", "hand this to a cheaper model", "run this in a worktree with model X", "check on that dispatched worker", "wait for the worker", or whe

• wb-branches

  Use WB to inventory and safely delete Git branches across the fleet — merged branches, stale branches, leftover branches that have no worktree, and stale remote branches. Use when asked to clean up branches, delete merged branches, prune remote branches, tidy leftover or historic branches, or audit

• wb-change

  Deliver a safe code change through WB worktrees, fleet-standard hooks, local verification, and coordinated pull requests. Use for implementation work, especially when multiple repositories or paired provider and consumer PRs must pass together.

• wb-ci

  Audit repository CI/CD policy with WB. Use when reviewing coverage gates, path-selective jobs, E2E setup duplication, artifact promotion, or whether CI policy findings should block a commit, push, or merge.

• wb-daemon

  Serve and inspect WB's local operations API and Cockpit web interface. Use when reviewing worktree activity and governed command cost, or when publishing a loopback WB service through an authenticated Cloudflare Tunnel.

• wb-dependency-campaign

  Plan and execute dependency release waves with the fewest safe GitHub Actions builds. Use for breaking changes, multiple newly published modules, provider-first rollouts, or any WB deps bump campaign that must reuse PRs and converge downstream consumers once.

• wb-deps

  Inspect dependency topology and convergence, then link consumers to a library's working tree or propagate published versions with WB. Use to find consumers, detect version drift or replaces, pin an exact GitHub Actions or Go version, plan release order, or update dependent repositories in verified w

• wb-fleet

  Synchronize, inspect, test, build, and measure local repository fleets with WB. Use for wb sync, status, coverage, verify, or check, especially when scope, parallelism, retries, and resumable reports can avoid repeated repository scans or CI runs.

• wb-hooks

  Install, inspect, repair, and price WB-managed Git hooks, including the cheap commit profile and the stream-branch push that defers to CI. Use when a repository needs fleet-standard pre-commit or pre-push checks, hook drift is reported, worktree policy must be enforced, or local hook cost and failur

• wb-install

  Install, update, and verify the WB CLI and its build provenance, and install or upgrade sibling fleet CLIs (specscore, codegrapher, cover100) relevant to wb via `wb install`/`wb upgrade`. Use when wb is missing, a required command or flag is unavailable, a task requires the exact build produced by a

• wb-merge

  Mechanically land one or many compatible completed WB branches/worktrees into the default or explicit target branch, choosing a verified direct-push or pull-request route, waiting for CI, synchronizing the canonical clone, and optionally cleaning up. Use `wb worktree land` (or its `wb land` alias) a

• wb-migrate

  Plan, apply, verify, resume, and publish declarative WB source migrations. Use when a versioned HCL migration should make deterministic code changes in one source root or coordinate provider-first changes across dependent Go repositories.

• wb-run

  Execute governed commands with telemetry and CPU admission, or list, preview, and apply reusable WB fleet recipes. Use for tests, builds, Git commands, command-cost history, and repeatable fleet recipes.

• wb-skills

  Install WB's own Agent Skills into this harness's skills directory (Claude Code ~/.claude/skills, Cursor ~/.cursor/skills, Codex ~/.codex/skills) and keep them current. Use at the start of any session where a wb-related skill (wb-worktrees, wb-merge, wb-hooks, wb-install, and the rest) seems to be m

• wb-streams

  Run one named cross-repository unit of work with WB streams — a library and the consumers that must change with it, each on a stream/<name> branch with a draft pull request, coordinated by wb stream start/join/status/end. Use when a change spans a library and its consumers, when a repository refuses

• wb-worktrees

  Use WB for the full isolated-worktree lifecycle: create, guard, inspect, resume, mechanically merge/land one or many completed worktrees to a default or target branch, synchronize the canonical clone, revert a landed batch forward, and safely clean branches/worktrees. Use before editing or branching

• wb

  Entry point for the WB CLI. Start work with `wb create <task> <owner/repository>...`, finish it with `wb worktree land`/`wb land` (one call per repository), `wb pr create` to open (or commit, push, open, and land in one call) a single worktree's pull request, or `wb pr land` for an already-open one

Subagents (1)

• wb-merger

  Dedicated foreground merger subagent for compatible completed WB work that proves remote receipt and clears lifecycle debt.

Similar plugins