Individual skill

workspace

Binds code repos and config overlays into a named workspace: shared identity in ~/.workspaces/, repo-local clones under .bridge/ with lockfiles. `workspace create` seeds it; `subscribe --role code` clones a repo; `subscribe --role config` delegates to /overlay. Trigger: "/workspace", "create a workspace", "add a repo to my workspace", "workspace status", "list workspaces".

skills/workspace/SKILL.md

Read pinned source

Source commit 2554bda8eeb2d55671e922c31484905fc8c67af9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Local scripts
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
13
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.