github-multi-repo

Coordinate and synchronize multiple GitHub repositories for cross-package dependency alignment.

1|Updated Nov 13, 2025
One-click install
npx skills add https://github.com/Cornjebus/amair --skill github-multi-repo-cornjebus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-multi-repo
Source: https://github.com/Cornjebus/amair/tree/main/.claude/skills/github-multi-repo
Command: npx skills add https://github.com/Cornjebus/amair --skill github-multi-repo-cornjebus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing consistency, dependencies, and architectural standards across multiple GitHub repositories can be a complex, error-prone, and time-consuming task, especially in large organizations or microservices architectures. This Skill automates and coordinates these efforts.

Core Features & Use Cases

  • Multi-Repository Swarm Coordination: Orchestrate AI agents across repositories for distributed development workflows.
  • Package Synchronization: Intelligently resolve dependencies and align package versions across multiple projects.
  • Repository Architecture Optimization: Analyze and optimize repository structures, and manage standardized templates.
  • Integration Management: Coordinate cross-package integration testing and deployment.
  • Use Case: Automatically synchronize a critical security library update across 50 microservice repositories, ensuring all dependencies are aligned, tests pass, and pull requests are created for review.

Quick Start

Initialize multi-repo coordination with a hierarchical topology: npx claude-flow skill run github-multi-repo init --repos "org/frontend,org/backend,org/shared" --topology hierarchical Synchronize package versions and dependencies: npx claude-flow skill run github-multi-repo sync --packages "claude-code-flow,ruv-swarm" --align-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 dependencies across multiple GitHub repositories?

Synchronize dependencies across repositories by defining your repos and running package alignment. The Skill resolves version conflicts, aligns package versions across projects, and generates pull requests for changes, ensuring consistent dependency management at scale.

Can I automate updates to a security library across dozens of microservices?

Yes. Coordinate multi-repository updates by specifying the package and target repos. The Skill orchestrates agents across repositories, tests the update in each, aligns dependent versions, and creates pull requests for review—automating propagation across your entire architecture.

What's the best way to maintain architectural consistency in a microservices organization?

Maintain consistency through architecture analysis and template management across repos. The Skill discovers repositories, analyzes structure, generates standardized templates, and coordinates cross-repo integration testing and deployment to enforce standards organization-wide.

How does multi-repository swarm coordination work for distributed development?

Swarm coordination deploys AI agents across repositories to work in parallel. The Skill orchestrates these agents to handle repository discovery, dependency resolution, architecture optimization, and cross-package integration testing in a hierarchical or distributed topology.

Do I need to manage each repository separately, or can I sync them together?

Sync them together. Rather than managing repos individually, define a multi-repo topology once. The Skill then coordinates package versions, aligns dependencies, synchronizes templates, and manages testing and deployment across all specified repositories automatically.

What happens when package versions conflict across repositories?

The Skill intelligently resolves conflicts by analyzing dependencies, identifying incompatibilities, and aligning versions to a compatible state across all repositories. It generates pull requests showing proposed changes, allowing teams to review and test before merge.