multi-repo

Coordinate multi-repo changes with dependency ordering and conflict resolution.

20|3|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/DVNghiem/FlowDeck --skill multi-repo-dvnghiem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-repo
Source: https://github.com/DVNghiem/FlowDeck/tree/main/src/skills/multi-repo
Command: npx skills add https://github.com/DVNghiem/FlowDeck --skill multi-repo-dvnghiem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating changes that span multiple repositories in a microservice architecture to maintain consistency across teams and services.

Core Features & Use Cases

  • Cross-repo planning and sequencing aligned with API contracts.
  • Conflict detection, dependency ordering, and rollout governance for multi-service changes.
  • Use Case: Orchestrate a feature update that touches user-service and order-service with a shared library upgrade.

Quick Start

Plan and execute a cross-repo change by updating the central registry, coordinating contracts, and rolling out in dependency order.

Frequently Asked Questions about multi-repo

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

FAQPage Schema
How do I coordinate changes across multiple repositories in a microservice architecture?

Coordinate multi-repo changes by using a central sub_repos registry to align API contracts, sequence rollouts by dependency order, and resolve conflicts across affected services.

How do I handle breaking API contract changes during a cross-service rollout?

Handle breaking API contract changes during cross-service rollouts by applying dependency ordering and conflict resolution mechanisms to sequence updates safely across affected repositories.

What is the best way to sequence a multi-repo feature update that touches shared libraries?

Sequence a multi-repo feature update by updating the central registry, aligning API contracts, and rolling out changes in strict dependency order to prevent service inconsistencies.

When do I need dependency ordering for microservice changes spanning multiple repos?

Dependency ordering is needed for multi-repo changes when a feature or fix touches two or more repos, ensuring shared library upgrades and cross-service rollouts execute without breaking dependencies.

Does this approach work for orchestrating updates across user-service and order-service?

Yes, this approach orchestrates updates across services like user-service and order-service by governing cross-repo planning, detecting conflicts, and rolling out shared library upgrades in correct dependency order.