github-multi-repo

Coordinates synchronization and architecture management across multiple GitHub repositories using swarm orchestration.

11|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/ishandutta2007/claude-agent-orchestration --skill github-multi-repo-ishandutta2007
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-multi-repo
Source: https://github.com/ishandutta2007/claude-agent-orchestration/tree/main/.claude/skills/github-multi-repo
Command: npx skills add https://github.com/ishandutta2007/claude-agent-orchestration --skill github-multi-repo-ishandutta2007

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ruv-swarm, gh-cli.

What problem does it solve? Managing changes across many GitHub repositories manually is error-prone: dependency versions drift, documentation diverges, and coordinated updates require repetitive cloning, testing, and PR creation for each repo. This Skill automates cross-repository coordination so organization-wide changes happen consistently. ## Core Features & Use Cases - Cross-Repository Swarm Orchestration: Discovers related repositories with the GitHub CLI and spawns coordinated AI agents to execute synchronized changes across all of them. - Package Synchronization: Aligns dependency versions, synchronizes documentation files like CLAUDE.md, and validates cross-package integration. - Repository Architecture Management: Analyzes repository structures, creates standardized project templates, and enforces consistent CI workflows across repos. - Use Case: Roll out a TypeScript 5.0 upgrade across every service repository in your organization: the Skill finds affected repos, updates each one, runs tests, opens labeled pull requests, and tracks everything in a central issue. ## Quick Start Ask the AI to initialize multi-repo coordination for your organization's frontend, backend, and shared repositories with hierarchical topology and synchronized dependency updates.

Frequently Asked Questions about github-multi-repo

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

FAQPage Schema
How do I update dependencies across multiple GitHub repositories at once?

Use the GitHub CLI to list organization repositories, clone each one, apply the dependency update, run tests, and open pull requests automatically. This Skill orchestrates that loop with swarm agents and tracks progress in a central issue.

How to synchronize package versions across a monorepo or multi-repo setup?

Read each package.json, align version fields, and commit updates through the GitHub API on a sync branch. The Skill stores synchronization status in shared memory so you can verify alignment across packages like claude-code-flow and ruv-swarm.

What tools are required to run multi-repository coordination?

You need the GitHub CLI (gh) version 2.0 or higher for repository operations and ruv-swarm 1.0.11 or higher for swarm orchestration. Node.js 20+ is required by the underlying claude-flow tooling.

Does this support different consistency models for cross-repo synchronization?

Yes, it supports eventual consistency with retry and backoff, strong consistency using raft consensus with quorum, and a hybrid mode where security updates use strong consistency while documentation syncs eventually.

Why do automated cross-repo updates fail on some repositories?

Failures typically occur when tests break after the update, permissions are insufficient, or webhooks are misconfigured. The Skill creates issue comments for failed repos and provides diagnose-connectivity and debug-memory commands for troubleshooting.

When should I use a monorepo instead of multi-repo coordination?

If repositories share tight coupling and frequent cross-package changes, migrating to a monorepo reduces synchronization overhead. The Skill includes a to-monorepo command that analyzes repos, suggests structure, and preserves git history during migration.