README
¶
WB agent skills
ai/skills/ is the canonical, harness-neutral source for WB's Agent Skills:
| Skill | Scope |
|---|---|
wb-install |
Install and verify an exact WB build |
wb-branches |
Inspect and safely retire local and remote branches |
wb-worktrees |
Guard, create, inspect, and clean worktrees |
wb-agents |
Dispatch a bounded task to a configured agent harness and inspect the run |
park |
Freeze a session or named task without starting a successor |
pickup |
Start a successor for a parked session or task |
move |
Transfer this whole session to a successor now |
offload |
Start a successor session for a portion of work |
wb-hooks |
Install, inspect, repair, and measure Git hooks |
wb-deps |
Graph, set, and bump dependencies |
wb-ci |
Audit CI/CD policy |
wb-migrate |
Run declarative source migrations |
wb-run |
Preview and apply reusable recipes |
wb-daemon |
Serve the local operations API and dashboard |
wb-fleet |
Sync, inspect, and verify repository fleets |
wb-change |
Deliver a safe multi-step code change |
wb-dependency-campaign |
Propagate releases with minimal CI builds |
wb-merge |
Integrate completed work and retire its lifecycle debt |
wb-skills |
Install these same skills into a harness's own skills directory |
The command-specific skills are compact references. The workflow skills compose them for workflows where orchestration saves time or avoids duplicate builds. Detailed flags live in references and load only when needed.
Claude Code recursively auto-discovers the same skills and root agents/
through the plugin described by .claude-plugin/plugin.json; the manifest does
not list them again. Codex reads the skills through
.codex-plugin/plugin.json and the per-skill agents/openai.yaml presentation
metadata. Marketplace packaging should reference this repository without
copying instructions; it is not included here. These checked-in adapters are
source, not proof that a harness has installed them. An installed wb-merge
adapter supersedes copied legacy merger prompts, which should be removed or
disabled so they cannot compete with the canonical contract.
That recursive auto-discovery only reaches a session working inside this
repository. A session orchestrating any other repository, with wb installed
globally, gets none of it -- there is no checkout of sneat-dev/wb to
recurse into. wb skills sync (wb-skills) is the separate mechanism for
that case. It passes the immutable plugin revision embedded in the installed
binary to github.com/strongo/cli-helpers/skillsync, which owns target
selection, locking, verified legacy-marker import, plugin-scoped ownership,
and crash-safe replacement. Ordinary sync is offline and matched to the
installed CLI; --newer-compatible is the only mode that may query for a newer
compatible published plugin revision. wb self-update runs the matched sync
automatically, and the SessionStart hook reports version drift once.
Completion contract
wb-change/references/completion.md
is the single definition of done for implementation work. It requires an agent
to report the achieved outcome as implemented, published, landed, or
blocked; it must never imply a push or merge happened without evidence. The
Codex default prompt routes to $wb-change, and Claude Code discovers the same
skill recursively, so neither harness maintains a competing copy.
skills/commands.json maps every public WB top-level
command to at least one skill. go test ./cmd/wb enforces that coverage as the
CLI evolves.
Capability delivery contract
capabilities.json is WB's single runtime/help/AI-skill/test delivery view.
Every public CLI leaf must have one conventionally named row; planned product
seams may add rows only when all four surfaces are honestly Planned and no
fictional command or example is exposed.
cli-capability-delivery.schema.json is a pinned vendored validation input,
not a second schema authority. Its canonical source is
specscore commit e06f6ab, path
new/cli-capability-delivery.schema.json, with schema ID
https://specscore.md/new/cli-capability-delivery.schema.json. The WB validator
in cmd/wb/skills_test.go pins the exact SHA-256 digest of that file before it
compiles the schema. An upstream schema update therefore fails until an
explicit migration replaces the vendored input, updates the digest, and makes
the manifest pass the new contract.
Documentation
¶
Overview ¶
Package ai embeds ai/skills -- WB's canonical, harness-neutral Agent Skills -- directly into the wb binary.
Every other consumer of ai/skills (Claude Code's own plugin auto-discovery, Codex's .codex-plugin manifest) reads it from a checked-out copy of this repository. That does nothing for the far more common case: wb installed as a standalone CLI (Homebrew, go install, a release archive) and run from an arbitrary project directory that is not, and has never been, a checkout of sneat-dev/wb. `wb skills sync` (strongo/cli-helpers/skillsync) installs these same skills into a harness's own skills directory (Claude Code ~/.claude/skills, Cursor ~/.cursor/skills, Codex ~/.codex/skills) so they are available everywhere wb is, and it must work from the installed binary alone -- so the source of truth is embedded here rather than read from disk at a repository path that may not exist.
Index ¶
Constants ¶
This section is empty.
Variables ¶
var SkillsFS embed.FS
SkillsFS holds every file under skills/ at build time: skills/<name>/ SKILL.md plus each skill's references/ and agents/ subdirectories. Keep this the only //go:embed directive over ai/skills; the shared sync adapter reads exclusively through this var so there is one embedded copy to keep in sync with the checked-in source.
Functions ¶
This section is empty.
Types ¶
This section is empty.
Source Files