# Coordinate multi-repository GitHub workflows

Managing multiple GitHub repositories requires coordinating changes, dependencies, and releases across repositories. This skill uses AI swarm orchestration to synchronize packages, standardize architecture, and coordinate cross-repository operations automatically.

## Install

```bash
npx skillstore add claude flow team/ruvnet-github-multi-repo
```

## Metadata

- - Slug: ruvnet-github-multi-repo
- - Version: 1.0.0
- - Author: Claude Flow Team
- - GitHub username: ruvnet
- - License: MIT
- - Repository: https://github.com/ruvnet/claude-flow/tree/main/.claude/skills/github-multi-repo
- - Ref: main
- - Supported tools: Claude, Claude Code
- - Risk level: safe
- - Risk factors: network, filesystem, external\_commands, env\_access
- - Quality score: 79
- - Quality tier: bronze
- - Public page: https://skillstore.pages.dev/skills/ruvnet-github-multi-repo
- - Manifest: https://skillstore.pages.dev/api/skills/ruvnet-github-multi-repo/manifest

## Capabilities

- Coordinate changes across multiple GitHub repositories using AI swarm orchestration
- Synchronize package versions and dependencies across repositories
- Analyze and optimize repository architecture with automated templates
- Create standardized project templates for new repositories
- Deploy security patches and dependency updates across all repositories
- Generate cross-repository dependency graphs and health reports

## Use Cases

- Synchronize microservices: Keep shared libraries and API contracts consistent across all microservices in your organization
- Coordinate cross-repo releases: Deploy coordinated releases across multiple repositories with synchronized version bumps
- Deploy security patches: Apply security updates to all repositories and create automated pull requests

## Prompt Templates

### Initialize coordination

```
Use github-multi-repo to initialize coordination for repositories: org/frontend, org/backend, org/shared with hierarchical topology
```

### Sync packages

```
Synchronize package versions for claude-code-flow and ruv-swarm. Align versions and update documentation across both repositories
```

### Standardize structure

```
Analyze repository structure and create standardized templates for new Claude Code projects in my organization
```

### Deploy security updates

```
Scan all my organization repositories for vulnerabilities, apply npm audit fixes, and create pull requests with security updates
```

## Limitations

- Requires GitHub CLI \(gh\) and claude-flow MCP server installation
- Cannot access private repositories without proper gh authentication
- Operates on repositories you have explicit access to via gh CLI
- Swarm operations depend on available MCP server resources

## Best Practices

- Use hierarchical topology for clear ownership and mesh for peer-to-peer coordination
- Create tracking issues before organization-wide changes to monitor progress
- Test changes in a single repository before propagating across all repositories

## Anti Patterns

- Running swarm operations without specifying repository boundaries
- Applying strong consistency sync for documentation changes
- Ignoring failed tests in individual repositories before propagating changes

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-01-17T07:28:36.048\+00:00
- - Summary: This is a pure documentation skill \(SKILL.md\) with no executable code. All security patterns detected are false positives - the file contains documentation examples showing how to use external tools \(gh CLI, claude-flow MCP\). These examples require explicit user invocation and operate only on repositories the user has access to via authenticated gh CLI.

## Stats

- - Views: 337
- - Downloads: 5
- - Favorites: 0
- - Popularity score: 0