agentleFS
Sign inStart free
metagit-aimetagit-ai/metagit-cli/.agents/skills/metagit-workspace-sync/SKILL.md

metagit-workspace-sync

Skill4 starsChanged 14 days agoMITView on GitHub

Sync workspace repositories safely using metagit with scoped fetch, pull, or clone actions. Use when repository content must be refreshed for implementation.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Use this skill when repository state must be updated.

    line 9
  2. Distinctive:

    Start with read-only status and fetch where possible.

    line 14
  3. Distinctive:

    Use pull/clone only when required for the current objective.

    line 15
  4. Distinctive:

    Avoid broad synchronization if only a subset is needed.

    line 35

≈ “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.

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

Syncing Workspace Repositories

Use this skill when repository state must be updated.

Workflow

  1. Confirm active workspace and target project.
  2. Start with read-only status and fetch where possible.
  3. Use pull/clone only when required for the current objective.
  4. Summarize which repositories changed and what remains stale.

Commands

  • metagit project sync --project <name>
  • MCP metagit_workspace_sync for batch fetch/pull/clone (repos, only_if, dry_run, max_parallel)
  • MCP metagit_repo_sync for a single repository (requires allow_mutation for pull/clone)
  • ./skills/metagit-control-center/scripts/control-cycle.sh [root_path] ["query"] [preset]

Output Contract

Return:

  • repositories synced
  • sync mode used (fetch/pull/clone)
  • failures and retry guidance

Safety

  • Limit sync to repos defined in .metagit.yml.
  • Avoid broad synchronization if only a subset is needed.

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