github-multi-repo

Coordinates synchronization, dependency updates, and architecture standardization across multiple GitHub repositories.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/wandreandrade2018-maker/claude-config --skill github-multi-repo-wandreandrade2018-maker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-multi-repo
Source: https://github.com/wandreandrade2018-maker/claude-config/tree/main/.claude/skills/github-multi-repo
Command: npx skills add https://github.com/wandreandrade2018-maker/claude-config --skill github-multi-repo-wandreandrade2018-maker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing changes across many GitHub repositories manually is slow and error-prone: dependency versions drift, documentation diverges, and organization-wide updates require repetitive cloning, editing, and PR creation for every repo. ## Core Features & Use Cases - Cross-Repository Swarm Orchestration: Discovers related repositories with the gh CLI and spawns coordinated AI agents to execute synchronized changes across all of them. - Package Synchronization: Aligns dependency versions and synchronizes shared documentation (like CLAUDE.md) across packages using the GitHub API. - Architecture Standardization: Analyzes repository structures, creates standardized templates, and pushes common files (CI workflows, configs) to every repository. - Use Case: Roll out a TypeScript 5.0 upgrade across all organization repositories: the skill finds every repo using TypeScript, updates each one, runs tests, and opens labeled pull requests tracked by a central issue. ## Quick Start Ask the AI to initialize multi-repo coordination for your organization's frontend, backend, and shared repositories and synchronize their dependency 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 update dependencies across multiple GitHub repositories at once?

Use the gh 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 through a central tracking issue.

How to synchronize package versions across repos in an organization?

Read each package.json via the GitHub API, align version fields, then push updated files on a sync branch using gh api PUT requests. The skill stores sync status in shared memory so alignment can be verified afterward.

What synchronization strategies exist for multi-repo coordination?

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

Does multi-repo coordination require the GitHub CLI?

Yes, the workflows rely on the gh CLI for repository discovery, cloning, PR creation, and GitHub API calls, plus claude-flow MCP tools for swarm initialization and shared memory. Both must be installed and authenticated.

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

Updates fail when tests break after the dependency change, when API permissions are insufficient, or when repositories lack expected files like package.json. The skill comments failures on the tracking issue instead of opening broken PRs.