# Coordinate Multi-Repository GitHub Workflows

Multi-repository programs are difficult to change consistently across dependencies, CI, and releases. This skill gives Claude, Codex, and Claude Code a structured process for analysis, migration, enforcement, and synchronized delivery.

## Install

```bash
npx skillstore add dnyoussef/when-managing-multiple-repos-use-github-multi-repo
```

## Metadata

- Status: approved
- Slug: dnyoussef-when-managing-multiple-repos-use-github-multi-repo
- Skillstore revision: r1
- Version status: missing
- Tree hash: 28dd45526a2f79f86cc9065d9e80c6de1fee131263a6dbe7c1a9ae296e99c123
- Author: DNYoussef
- GitHub username: DNYoussef
- License: MIT
- Repository: https://github.com/DNYoussef/ai-chrome-extension/tree/main/.claude/skills/github-integration/when-managing-multiple-repos-use-github-multi-repo
- Ref: 0519034dad657fb1f7706e0550e962beeda73fdf
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/dnyoussef-when-managing-multiple-repos-use-github-multi-repo
- Manifest: https://skillstore.pages.dev/api/skills/dnyoussef-when-managing-multiple-repos-use-github-multi-repo/manifest

## Capabilities

- Defines a hierarchical agent workflow for coordinating changes across multiple repositories.
- Maps repository dependencies and uses graph output to plan update order.
- Guides monorepo migration into focused repositories while preserving Git history.
- Coordinates synchronized pull requests, testing, versioning, and releases.
- Describes architecture compliance scanning and remediation workflows.
- Shows MCP tool calls for GitHub analysis and swarm task tracking.

## Use Cases

- Propagate Shared API Changes: Plan and sequence updates when one service contract affects several dependent repositories.
- Split a Monorepo Safely: Design target repositories, preserve history, update dependencies, and validate the cutover plan.
- Enforce Architecture Standards: Scan related repositories for policy drift and create a coordinated remediation plan.

## Prompt Templates

### Map Repository Dependencies

```
Analyze these repositories and identify direct dependencies, shared packages, and likely update order. Return a short dependency map and review risks.
```

### Plan a Cross-Repo Change

```
Create a coordinated change plan for this API update across the affected repositories. Include sequencing, tests, owners, draft pull requests, and rollback steps.
```

### Design a Monorepo Split

```
Review this monorepo structure and propose target repositories. Include module boundaries, dependency changes, history preservation, CI changes, and validation gates.
```

### Coordinate a Synchronized Release

```
Build a synchronized release plan for these repositories. Include dependency order, version strategy, integration tests, merge rules, release notes, and rollback criteria.
```

## Limitations

- It does not include the referenced shell scripts or templates.
- It requires approved access to target repositories and GitHub tooling.
- It cannot guarantee changes are correct without project tests and reviews.
- It assumes teams can run MCP tools and external repository commands safely.

## Best Practices

- Review every generated plan before any repository write operation.
- Run changes in dependency order and keep rollback tags for coordinated releases.
- Use dry runs and draft pull requests before merges or releases.

## Anti Patterns

- Do not run relative shell scripts from a workspace before reviewing their contents.
- Do not merge downstream repositories before shared dependencies are released.
- Do not let worker agents change repository architecture without coordinator review.

## Security Audit

- Audited at: 2026-07-09T12:12:32.458\+00:00
- Summary: The static Ruby backtick findings are false positives because they point to Markdown fences, inline identifiers, or prose. The semantic review found risk in unpinned npx execution and repeated instructions to run relative workspace scripts that perform writes. No prompt injection or data exfiltration language was found.

## Stats

- Views: 298
- Downloads: 8
- Favorites: 0
- Popularity score: 0