mcpbeat

When Managing Multiple Repos Use Github Multi Repo

comeonoliver/when-managing-multiple-repos-use-github-multi-repo

Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration. Coordinates repo-architect, code-analyzer, and coordinator agents across multiple repositories to maintain consistency, propagate changes, manage dependencies, and ensure architectural alignment. Handles monorepo-to-multi-repo migrations, cross-repo refactoring, and synchronized releases. Use when managing microservices, multi-package ecosystems, or coordinating changes across related repositories.

10k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
1
copies elsewhere
how many repositories repackaged it
59
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/ComeOnOliver/skillshub --skill when-managing-multiple-repos-use-github-multi-repo

Repackaged in 1 other repositories

same content, different owner
aiskillstore/marketplace open on GitHub →

How to use it

Copy the folder

Take comeonoliver/when-managing-multiple-repos-use-github-multi-repo from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npx. Without those the skill loads but fails at the first command.