workspacelisted

Bind code repos AND config overlays into a named WORKSPACE — a project container with a machine-global identity (shared with any conformant tool via ~/.workspaces/) and repo-local materialization (clones under .bridge/, lockfiles, a public-fork-safe exclude guard). `workspace create <name>` seeds the definition; `subscribe … --role code` clones a member repo; `subscribe … --role config` delegates a config overlay to the /overlay engine; `list` / `status` / `validate` inspect; `unsubscribe` removes. Standalone — zero dependency on any external launcher; the shared identity write is additive and warns-never-fails. Trigger: "/workspace", "workspace", "create a workspace", "add a repo to my workspace", "bind repos", "workspace status", "list workspaces", "subscribe repo to workspace", "unsubscribe from workspace", "workspace members", "project container".
bks-lab/open-bridge · ★ 8 · AI & Automation · score 74

Install: claude install-skill bks-lab/open-bridge

# Workspace — bind repos + config into one named project container A **workspace** is a named project identity that pulls together the code repos and config overlays you work on as one unit. It has two disjoint halves: - **Identity** (*which project is this*) — name, member roots, git remotes — lives in the **machine-global shared registry** `~/.workspaces/workspaces.json`, a tool-neutral file any conformant tool can read/write under a documented lock + atomic-replace protocol. This is how a workspace means the same thing across tools on the machine. - **Materialization** (*how does THIS repo realise it*) — the actual clones, the resolved-SHA lockfile, the fork-safety exclude block — is **repo-local** and never leaves the repo. The engine is `scripts/workspace.py` (standalone, stdlib-only) — a shared repo-root utility shipped with the Bridge repo itself, not a file inside this skill's own directory. This skill is the `/workspace` surface over it. **Run the referenced file ONLY when the decision tree sends you there.** `/workspace` is the **umbrella**; for the deep *org-overlay* subscription flow (manifest validation, per-file plan, 3-way merge, sync/diff) it delegates to and cross-references **`/overlay`** (the `bridge-overlay` skill). Binding a config overlay via `workspace subscribe … --role config` calls that same engine (`overlay.py`) under the hood. ## When to use - "Make a workspace for project X" → `create` - "Add this repo to the workspace" / "bind t