agentleFS
Sign inStart free
metagit-aimetagit-ai/metagit-cli/skills/metagit-multi-repo/SKILL.md

metagit-multi-repo

Skill4 starsChanged 13 days agoMITView on GitHub

Coordinate implementation tasks across multiple repositories using metagit status, search, and scoped sync workflows. Use when one objective spans several repositories.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for cross-repository feature or fix delivery.

    line 7
  2. Distinctive:

    Verify workspace scope and dependency hints.

    line 12
  3. Very specific:

    When running parallel agents on the same repo, isolate with skill metagit-agent-coordination (branch → lease → worktree) before edits.

    line 15
  4. Distinctive:

    Keep scope bounded to configured workspace repositories.

    line 31
  5. Distinctive:

    Prefer deterministic evidence for cross-repo assumptions.

    line 32

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

Coordinating Multi-Repo Implementation

Use this skill for cross-repository feature or fix delivery.

Workflow

  1. Define objective and affected repositories.
  2. Verify workspace scope and dependency hints.
  3. Sequence work by dependency order.
  4. Sync only required repositories.
  5. When running parallel agents on the same repo, isolate with skill metagit-agent-coordination (branch → lease → worktree) before edits.
  6. Track progress and blockers per repository.

Command Wrapper

  • ./skills/metagit-control-center/scripts/control-cycle.sh [root_path] ["query"] [preset]

Output Contract

Return:

  • objective-to-repository map
  • execution order
  • current blocker + next step

Safety

  • Keep scope bounded to configured workspace repositories.
  • Prefer deterministic evidence for cross-repo assumptions.

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