using-workspaces
Skill9 starsChanged 10 months agoMITView on GitHub
Overview and getting started guide for the workspaces plugin. Use when user asks "how do I use workspaces", "workspaces help", or "getting started with workspaces".
In this repository8 other files it gives its agents.
- workspace-affectedSkill
- workspace-cloneSkill
- workspace-doctorSkill
- workspace-initSkill
- workspace-searchSkill
- workspace-servicesSkill
- workspace-setupSkill
- workspace-statusSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
When the user asks about using the workspaces plugin, provide this overview:
- Distinctive: line 24
Add your projects with their repos, paths, and ports
- Distinctive: line 30
Run setup scripts (install deps, migrations, etc.)
- Distinctive: line 33
Check prerequisites and run health checks
- Very specific: line 59
Use /workspaces:affected api to see what depends on the API before making breaking changes
- Very specific: line 60
Use /workspaces:search "TODO" to find TODOs across all projects
- Very specific: line 61
Run /workspaces:doctor when something isn't working
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Using Workspaces
Description
This skill provides an overview of the workspaces plugin and how to use it effectively for managing multi-project/multi-repo workflows.
Instructions
When the user asks about using the workspaces plugin, provide this overview:
Workspaces Overview
The workspaces plugin helps you manage multiple related repositories that belong to the same company or project. Perfect for teams working with microservices, polyrepos, or any multi-project setup.
Quick Start
- Initialize a workspace:
/workspaces:init- Creates a new workspace configuration
- Add your projects with their repos, paths, and ports
- Clone repositories:
/workspaces:clone all- Clone all configured repos to their designated paths
- Set up projects:
/workspaces:setup all- Run setup scripts (install deps, migrations, etc.)
- Verify everything:
/workspaces:doctor- Check prerequisites and run health checks
- Check status:
/workspaces:status- See git status, branches, and running services across all projects
Configuration
Workspace configs are stored in ~/.claude/workspaces/<workspace-name>/:
WORKSPACE.md- Main configuration with projects, relationships, and commands
Available Commands
| Command | Description |
/workspaces:init | Create a new workspace |
/workspaces:status | Show status across all projects |
/workspaces:clone | Clone repositories |
/workspaces:setup | Run setup scripts |
/workspaces:start | Start services |
/workspaces:stop | Stop services |
/workspaces:affected | Show dependency graph |
/workspaces:search | Search across all projects |
/workspaces:doctor | Check prerequisites and health |
Tips
- Use
/workspaces:affected apito see what depends on the API before making breaking changes - Use
/workspaces:search "TODO"to find TODOs across all projects - Run
/workspaces:doctorwhen something isn't working
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.