Skip to content
Skills Library
Programming · Automation

github-multi-repo

/github-multi-repo

Coordinate work across many GitHub repositories at once — org-wide dependency/security updates, package and doc version alignment, cross-repo refactors, and shared architecture/templates. Use when a change must land in several repos together, not for single-repo review, release, or CI tasks.

Repository
agentbox ↗
Licence
AGPL-3.0
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.

What it does and when to use it

Coordinate work across many GitHub repositories at once — org-wide dependency/security updates, package and doc version alignment, cross-repo refactors, and shared architecture/templates. Use when a change must land in several repos together, not for single-repo review, release, or CI tasks.

Original author description

Coordinate work across many GitHub repositories at once — org-wide dependency/security updates, package and doc version alignment, cross-repo refactors, and shared architecture/templates. Use when a change must land in several repos together, not for single-repo review, release, or CI tasks.

How it works

  1. When to use
  2. When not to use
  3. Safety — org-wide operations are hard to reverse
  4. Quick start
  5. Core capabilities
  6. References
Original SKILL.md headings · 86 lines, 482 words
SKILL.md preview
---
name: github-multi-repo
version: 1.0.0
description: "Coordinate work across many GitHub repositories at once — org-wide dependency/security updates, package and doc version alignment, cross-repo refactors, and shared architecture/templates. Use when a change must land in several repos together, not for single-repo review, release, or CI tasks."
category: github-integration
tags: [multi-repo, synchronization, architecture, coordination, github]
author: Claude Flow Team
requires:
  - ruv-swarm@^1.0.11
  - gh-cli@^2.0.0
---

# GitHub Multi-Repository Coordination

Coordinate AI swarms, package synchronisation, and architecture across multiple
repositories: organisation-wide automation, cross-project changes, and scalable
repository management. Combines `gh` CLI, `claude-flow` swarm MCP tools, and
agent orchestration.

## When to use
- A single change must land across several repos in step (dependency bumps,
  security patches, policy files, shared CI workflows).
- Aligning package versions or documentation across packages/monorepo members.
- Discovering related repos, mapping cross-repo dependencies, or standardising
  structure/templates org-wide.

## When not to use
- Single-repository code review → `github-code-review`.
- Release management within one repo → `github-release-management`.
- GitHub Actions workflow authoring → `github-workflow-automation`.
- Issue tracking / sprint planning → `github-project-management`.
- Cloud swarm deployment unrelated to GitHub repos → `flow-nexus-swarm`.

## Safety — org-wide operations are hard to reverse
Cross-repo pushes touch many repositories in one sweep and are not locally
reversible once fanned out. Before running a fan-out that pushes, opens PRs, or
mutates files across an org:
- Scope the repo filter tightly and dry-run the discovery step first (list the
  repos that would be touched before acting on them).
- Prefer opening PRs over direct pushes so each change is reviewable per repo.
- For genuinely irreversible org-wide sweeps (force pushes, protected-branch or
  policy changes), get explicit human sign-off before executing — treat this as a
  hard gate, not a default.
This is the one guard-railed path in the skill; everything else is judgment-based.

## Quick start

```bash
# Initialize multi-repo coordination (hierarchical topology)
npx claude-flow skill run github-multi-repo init \
  --repos "org/frontend,org/backend,org/shared" \
  --topology hierarchical

# Mesh topology with shared memory + eventual-consistency sync
npx claude-flow skill run github-multi-repo init \
  --repos "org/frontend,org/backend,org/shared" \
  --topology mesh --shared-memory --sync-strategy eventual

# Synchronize package versions and dependencies
npx claude-flow skill run github-multi-repo sync \
  --packages "claude-code-flow,ruv-swarm" --align-versions --update-docs

# Analyze and optimize repository structure
npx claude-flow skill run github-multi-repo optimize \
  --analyze-structure --suggest-improvements --create-templates
```

**Claude Code only:** the swarm orchestration above (`claude-flow skill run`) needs the
claude-flow MCP server. On Codex / GPT-6 Astra (or any session without it): see
[../github-code-review/references/plain-gh-fallback.md](../github-code-review/references/plain-gh-fallback.md)
for the plain `gh`-only path (the org-wide safety rules above still apply).

## Core capabilities
- **Multi-repository swarm coordination** — cross-repo AI swarm orchestration for
  distributed workflows.
- **Package synchronisation** — dependency resolution and version alignment across
  packages.
- **Repository architecture** — structure optimisation and template management.
- **Integration management** — cross-package integration testing and deployment.

## References
- **[references/cookbook.md](references/cookbook.md)** — runnable recipes: swarm
  discovery/synchronised ops, package + doc version alignment, cross-package
  features, architecture analysis, template creation, standardisation, and the
  org-wide dependency/refactor/security-patch workflows.
- **[references/configuration.md](references/configuration.md)** — `.swarm/multi-repo.yml`
  config, repository roles, webhook/Kafka communication strategies, eventual/strong/
  hybrid sync patterns, and monorepo/command-structure layouts.
- **[references/operations.md](references/operations.md)** — the
  `skill run github-multi-repo <verb>` operational surface (use cases, dashboards,
  dep-graph, health checks, caching/parallel/resource tuning, troubleshooting,
  advanced features, metrics), plus related-skill integration points.

---

**Version:** 1.0.0 · **Last Updated:** 2026-07-28 · **Maintainer:** Claude Flow Team
Files in this package (4)
  • SKILL.md 5 KB
  • references/configuration.md 4 KB
  • references/cookbook.md 12 KB
  • references/operations.md 5 KB

Versions

RepositoryScoreLicence
This page · dreamlab-ai/agentbox100AGPL-3.0
frankxai/claude-skills-library100MIT

Database snapshot: 13.11.2026 · package version 528b4349c98e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100cross-repo-refactor
    Coordinate a multi-repo refactor by fanning out subagents per repo onto one feature branch. Use for cross-repo changes that touch multiple repositories.
  • 100git-repo-detection
    Detect GitHub repo owner/name from git remotes. Use when needing the owner/repo identifier for GitHub CLI or API calls, especially across multiple repos.
  • 95github-repo-maintainer
    Maintains GitHub repositories by inspecting project structure, reviewing code and issues, improving documentation, planning safe refactors, preparing tests and release notes, and proposing focused changes when the user asks for repository work.
  • 100my-repos
    Locate and work with dwmkerr's repositories. Use when user mentions "my repos", "my repo X", "check my repo", or needs to find/access a specific repository.
  • 100github-repo-architect
    Convert a repository idea into a complete GitHub repository architecture. Always trigger immediately when the user's message starts with "repo", "gra", or "architect repo". Also trigger on "build a repo structure", "design a GitHub repo", "scaffold this repository", "create…
  • 86gh-org-backup
    Back up every GitHub repo the user can read in one organization (or their whole account) into a single zip, with every branch checked out locally. Use when the user wants to download, back up, archive, export, mirror or zip all repos of a GitHub org or account.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.