github-multi-repo

Automate cross-repository coordination and synchronization across multiple GitHub repositories.

Updated Sep 21, 2025
One-click install
npx skills add https://github.com/bjpl/california_puzzle_game --skill github-multi-repo-bjpl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-multi-repo
Source: https://github.com/bjpl/california_puzzle_game/tree/main/.claude/skills/github-multi-repo
Command: npx skills add https://github.com/bjpl/california_puzzle_game --skill github-multi-repo-bjpl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ruv-swarm@^1.0.11, gh-cli@^2.0.0.

What problem does it solve?

Managing and synchronizing changes across multiple GitHub repositories can be a complex, error-prone, and time-consuming task, especially in microservices architectures or large organizations. This skill automates cross-repository coordination.

Core Features & Use Cases

  • Multi-Repository Swarm Coordination: Orchestrate AI swarms to manage distributed development workflows across repositories.
  • Package Synchronization: Align package versions, dependencies, and documentation across projects.
  • Architecture Optimization: Analyze and optimize repository structures, create templates, and enforce standardization.
  • Use Case: Synchronize a critical security patch across 50 microservice repositories, ensuring all dependencies are updated, tests pass, and pull requests are automatically created and tracked.

Quick Start

Initialize multi-repo coordination for "org/frontend", "org/backend", and "org/shared" with a hierarchical topology. Then, synchronize "claude-code-flow" and "ruv-swarm" packages, aligning their versions.

Frequently Asked Questions about github-multi-repo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I synchronize packages and dependencies across multiple GitHub repositories?

Package synchronization aligns versions and dependencies across repositories by analyzing the entire multi-repo ecosystem, identifying version mismatches, and applying consistent updates. This Skill automates cross-repository dependency alignment using gh-cli and swarm orchestration to ensure all projects use compatible package versions.

Can I automate coordinated pull requests and testing across multiple repositories?

Yes. This Skill automates test and PR creation across repositories by orchestrating changes as a coordinated swarm, running tests in parallel, and tracking pull requests centrally. It enables reproducible, scalable deployments across dozens of repositories simultaneously.

What's the best way to manage a microservices architecture with 50+ repositories?

Multi-repository swarm coordination discovers all repositories, analyzes their interdependencies, and orchestrates synchronized changes across the entire architecture. This Skill applies hierarchical topology management, template generation, and automated architecture optimization to enforce standardization at scale.

How do I apply a security patch uniformly across all my organization's repositories?

Cross-repository coordination uses swarm orchestration to discover all affected repositories, align versions, apply patches, run tests, and auto-generate pull requests. This ensures consistent patch deployment and verification across microservice repositories without manual intervention per repository.

Do I need existing GitHub repository templates before using multi-repo automation?

No, but this Skill generates and enforces templates as part of architecture optimization. It analyzes current repository structures, identifies standardization opportunities, and creates templates to apply consistency across frontend, backend, and shared library repositories.

What are the limitations of automating changes across many repositories at once?

Swarm coordination requires gh-cli and ruv-swarm dependencies installed and proper repository permissions. Success depends on repository structure consistency, network stability during parallel operations, and test suite reliability. Preview modes and dependency analysis help validate changes before large-scale deployment.