skills.rest
rysweet
rysweetCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

multi-repo

Orchestrate atomic changes across multiple repositories with linked pull requests.

1|Updated Nov 11, 2025
Search Tags:#ci/cd#dependency management#breaking changes#orchestration#pull requests#multi-repo
One-click install
npx skills add https://github.com/rysweet/RustyClawd --skill multi-repo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: multi-repo
Source: https://github.com/rysweet/RustyClawd/tree/main/.claude/skills/multi-repo
Command: npx skills add https://github.com/rysweet/RustyClawd --skill multi-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines development workflows by enabling coordinated, atomic changes across multiple repositories, preventing integration issues and ensuring consistency.

Core Features & Use Cases

  • Dependency Management: Define and visualize relationships between repositories.
  • Breaking Change Detection: Proactively identify potential impacts of changes on dependent projects.
  • Linked Pull Requests: Create and manage sets of PRs that must be merged together or in a specific order.
  • Use Case: When updating a shared API, this skill can detect which microservices depend on it, flag any breaking changes, and help create linked PRs for the API update and the corresponding microservice fixes.

Quick Start

Initialize the multi-repo dependencies for this project.

Frequently Asked Questions about multi-repo

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

FAQPage Schema
How do I coordinate atomic changes across multiple repositories?▼

To coordinate atomic changes across multiple repositories, you can use a dependency graph to manage linked pull requests. This ensures updates are merged sequentially based on repository dependencies, preventing integration issues.

How do I detect breaking changes in microservice dependencies before merging?▼

Detecting breaking changes in microservice dependencies is handled by orchestrating atomic changes across multiple repositories. The system proactively identifies potential impacts on dependent projects to ensure consistency.

What is the best way to manage linked pull requests across different repositories?▼

Managing linked pull requests across different repositories is best achieved by defining a dependency graph and orchestrating atomic changes. This creates sets of PRs that must be merged together or in a specific order.

How do I configure repository dependencies for local development?▼

Configuring repository dependencies for local development requires using YAML configuration files. This setup integrates with worktree management to visualize relationships and coordinate changes across your repositories.

Does multi-repo orchestration work with existing CI/CD pipelines?▼

Multi-repo orchestration works with your development workflow by managing dependency graphs and coordinating linked pull requests. It ensures sequential merging based on repository dependencies to maintain consistency across your projects.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
az9713az9713
2

land-and-deploy

Merge pull requests, deploy code, and verify production health.

Community
Advanced
heaptracetechnologyheaptracetechnology
13

contract-test

Automate API contract testing with schema validation and OpenAPI checks.

Community
Advanced
pacphipacphi
6

github-multi-repo

Coordinate and synchronize multiple GitHub repositories using swarm-based orchestration.

Community
Advanced