github-multi-repo

To synchronize dependencies across multiple GitHub repositories, this Skill discovers related codebases via gh CLI and uses swarm orchestration to align package versions, update documentation, and automatically generate pull requests that eliminate version drift across services.

Cross-repository swarm orchestration deploys multiple specialized AI agents to plan and execute coordinated changes across related GitHub codebases simultaneously, ensuring synchronized state tracking and consistent architecture without manual intervention.

Yes, both ruv-swarm and gh CLI are required. The gh CLI handles GitHub repository discovery and API interactions, while ruv-swarm provides the parallel task orchestration topology required for synchronized state propagation across repositories.

You can standardize repository templates by analyzing existing codebase structures for scalability bottlenecks, applying recommended architecture improvements, and propagating standardized templates across the organization using coordinated multi-repo workflows.

The best way to roll out a dependency upgrade across dozens of GitHub services is using coordinated multi-repo orchestration to apply changes in parallel, maintain integration test confidence, and automatically produce pull requests for each affected repository.

Architecture fragmentation happens in distributed multi-repo workflows because related codebases evolve independently without synchronized state tracking, causing inconsistent documentation, dependency drift, and structural divergence that requires coordinated cross-repo automation to resolve.