agentleFS
Sign inStart free
mazze93mazze93/claude-code-skills/skills/workspace-sync/SKILL.md

workspace-sync

Skill1 starsChanged 11 days agoMITView on GitHub

Reconcile the ~/Projects workspace against WORKSPACE.md and GitHub — clone missing repos into their domains, report drift, add/move projects with map-and-territory discipline. Use when asked to "sync the workspace", "clone my repos", "add a repo to the workspace", or "check workspace status".

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never git add a project into the container — the allowlist .gitignore and pre-commit hook will fight you.

    line 48

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/workspace-sync

The workspace root ~/Projects (alias ~/Code) is a thin container repo (mazze93/projects-workspace); every project is a sibling clone under a domain dir. WORKSPACE.md is the map and the intent — if disk and map disagree, reconcile toward the map.

Commands (all via ~/Projects/scripts/ws)

scripts/ws list      # registry vs disk (✓/✗)
scripts/ws status    # dirty/ahead/behind across every clone
scripts/ws sync      # ff-pull every clean clone (dirty ones skipped, never touched)
scripts/ws missing   # clone absent registry entries into their domain paths
scripts/ws open <q>  # fuzzy-open a project in Zed

Adding a new project (the contract, rule 3)

  1. Decide its domain: blog/ apps/ tools/ cognitive/ creative/ secure-pride/ skills/ templates/ meta/ archive/. Doesn't fit? STOP and ask — never invent a top-level dir.
  2. In the SAME commit to the container: add its row to the WORKSPACE.md registry AND its "path|repo" line to the REGISTRY array in scripts/ws.
  3. scripts/ws missing to clone it. Commit message: map: add <name> to <domain>/.

Moving / retiring a project

Same-commit rule applies: mv the dir, update both registry locations, commit. Retired repos go to archive/, not deleted.

Full resync on a fresh machine

gh auth login
gh repo clone mazze93/projects-workspace ~/Projects
cd ~/Projects && bash scripts/install-hooks.sh && bash scripts/ws missing
ln -sfn ~/Projects ~/Code

Guardrails

  • Never git add a project into the container — the allowlist .gitignore and pre-commit hook will fight you; they are right.
  • secure-pride/* stays in private repos; never log identifiers unmasked.
  • New GitHub repos that are empty (0 KB) are listed under "Not cloned" in WORKSPACE.md rather than cloned.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free