Multi-Repo Orchestrator FAQs

Question 1

Does this require a centralized database for tracking dependencies?

Accepted Answer

No, it follows a philosophy of ruthless simplicity by using YAML-based files stored locally in your home directory, making it easy to manage without additional infrastructure.

Question 2

How does this skill detect breaking changes across repositories?

Accepted Answer

The skill scans modifications to public interfaces, such as OpenAPI specs or exported schemas, identifies dependent repositories in the local dependency graph, and analyzes those dependents to report potential impacts before PRs are created.

Question 3

How does it handle the merging of linked Pull Requests?

Accepted Answer

It implements a merge sequence logic that respects your dependency graph, ensuring that upstream dependencies (like a core API) are merged and verified before downstream consumers (like a mobile app) are merged.

Question 4

Can I use this for local development across multiple folders?

Accepted Answer

Yes, the skill integrates with git worktrees to create isolated workspaces for each repository involved in a change set, allowing you to edit, test, and commit across repos simultaneously.

Question 5

What tools are required for the PR features to work?

Accepted Answer

The skill leverages the GitHub CLI (gh) for all Pull Request operations, so you must be authenticated with GitHub to use the automated PR creation and merging features.

Multi-Repo Orchestrator

Multi-Repo Orchestrator

Key Features

Use Cases

Key Features

Use Cases