
Github Multi Repo
Coordinate changes, dependencies, and architecture across several GitHub repos with swarm-assisted sync and distributed workflows.
Overview
GitHub Multi-Repo is an agent skill most often used in Build (also Ship, Operate) that coordinates multiple GitHub repositories with swarm orchestration, package sync, and architecture templates.
Install
npx skills add https://github.com/ruvnet/ruflo --skill github-multi-repoWhat is this skill?
- Multi-repository swarm coordination for distributed dev workflows
- Package synchronization with dependency resolution and version alignment
- Repository architecture optimization and template management
- Cross-package integration testing and deployment coordination
- CLI init via claude-flow with org/repo lists and topology flags; requires ruv-swarm and GitHub CLI
- Frontmatter requires ruv-swarm@^1.0.11 and gh-cli@^2.0.0
- Documents four core capability areas: swarm coordination, package sync, architecture, and integration management
Adoption & trust: 645 installs on skills.sh; 58.5k GitHub stars; 0/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your product spans several GitHub repos and versions drift, PRs conflict, and nobody has a single playbook for cross-repo releases.
Who is it for?
Indie orgs with 2+ related GitHub repos who already use GitHub CLI and want swarm-assisted sync and integration testing.
Skip if: Single-repo side projects or builders who cannot install ruv-swarm, authenticate gh, or maintain multi-repo topology configuration.
When should I use this skill?
You need multi-repository GitHub coordination, package synchronization, architecture templates, or distributed workflows with ruv-swarm and gh-cli.
What do I get? / Deliverables
You get initialized multi-repo coordination, aligned packages, and distributed workflows so changes land consistently across frontend, backend, and shared libraries.
- Multi-repo coordination configuration and topology
- Synchronized dependency versions across listed packages
- Cross-repo integration and deployment coordination plan
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build is the primary shelf because the skill is about cross-repo coordination, package alignment, and integration management while you are actively developing multiple codebases. Integrations captures cross-repository linking, dependency sync, and cross-package testing—not single-repo frontend or isolated backend work.
Where it fits
Init coordination across org/frontend, org/backend, and org/shared with hierarchical swarm topology.
Run cross-package integration checks before merging a version bump that spans three repos.
Re-align shared package versions after a hotfix landed in only one repository.
How it compares
Cross-repo coordination with swarm and gh-cli—not a simple single-PR review skill or a local lint-only checker.
Common Questions / FAQ
Who is github-multi-repo for?
Solo builders and small teams managing multiple GitHub repositories who need synchronized dependencies, templates, and coordinated agent workflows across repos.
When should I use github-multi-repo?
In Build when wiring integrations across frontend/backend/shared packages; in Ship when coordinating cross-repo releases and integration tests; and in Operate when iterating infra or shared libraries that touch many repos.
Is github-multi-repo safe to install?
It uses shell, git, and GitHub API access across organizations—check the Security Audits panel on this Prism page and limit repo scope before running swarm init in production orgs.
SKILL.md
READMESKILL.md - Github Multi Repo
# GitHub Multi-Repository Coordination Skill ## Overview Advanced multi-repository coordination system that combines swarm intelligence, package synchronization, and repository architecture optimization. This skill enables organization-wide automation, cross-project collaboration, and scalable repository management. ## Core Capabilities ### 🔄 Multi-Repository Swarm Coordination Cross-repository AI swarm orchestration for distributed development workflows. ### 📦 Package Synchronization Intelligent dependency resolution and version alignment across multiple packages. ### 🏗️ Repository Architecture Structure optimization and template management for scalable projects. ### 🔗 Integration Management Cross-package integration testing and deployment coordination. ## Quick Start ### Initialize Multi-Repo Coordination ```bash # Basic swarm initialization npx claude-flow skill run github-multi-repo init \ --repos "org/frontend,org/backend,org/shared" \ --topology hierarchical # Advanced initialization with synchronization npx claude-flow skill run github-multi-repo init \ --repos "org/frontend,org/backend,org/shared" \ --topology mesh \ --shared-memory \ --sync-strategy eventual ``` ### Synchronize Packages ```bash # Synchronize package versions and dependencies npx claude-flow skill run github-multi-repo sync \ --packages "claude-code-flow,ruv-swarm" \ --align-versions \ --update-docs ``` ### Optimize Architecture ```bash # Analyze and optimize repository structure npx claude-flow skill run github-multi-repo optimize \ --analyze-structure \ --suggest-improvements \ --create-templates ``` ## Features ### 1. Cross-Repository Swarm Orchestration #### Repository Discovery ```javascript // Auto-discover related repositories with gh CLI const REPOS = Bash(`gh repo list my-organization --limit 100 \ --json name,description,languages,topics \ --jq '.[] | select(.languages | keys | contains(["TypeScript"]))'`) // Analyze repository dependencies const DEPS = Bash(`gh repo list my-organization --json name | \ jq -r '.[].name' | while read -r repo; do gh api repos/my-organization/$repo/contents/package.json \ --jq '.content' 2>/dev/null | base64 -d | jq '{name, dependencies}' done | jq -s '.'`) // Initialize swarm with discovered repositories mcp__claude-flow__swarm_init({ topology: "hierarchical", maxAgents: 8, metadata: { repos: REPOS, dependencies: DEPS } }) ``` #### Synchronized Operations ```javascript // Execute synchronized changes across repositories [Parallel Multi-Repo Operations]: // Spawn coordination agents Task("Repository Coordinator", "Coordinate changes across all repositories", "coordinator") Task("Dependency Analyzer", "Analyze cross-repo dependencies", "analyst") Task("Integration Tester", "Validate cross-repo changes", "tester") // Get matching repositories Bash(`gh repo list org --limit 100 --json name \ --jq '.[] | select(.name | test("-service$")) | .name' > /tmp/repos.txt`) // Execute task across repositories Bash(`cat /tmp/repos.txt | while read -r repo; do gh repo clone org/$repo /tmp/$repo -- --depth=1 cd /tmp/$repo # Apply changes npm update npm test # Create PR if successful if [ $? -eq 0 ]; then git checkout -b update-dependencies-$(date +%Y%m%d) git add -A git commit -m "chore: Update dependencies" git push origin HEAD gh pr create --title "Update dependencies" --body "Automated up