orchestrate-multi-repo-sdks

Dispatch SDK generation and reconcile PRs across multiple language repositories.

19|6|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/speakeasy-api/skills --skill orchestrate-multi-repo-sdks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrate-multi-repo-sdks
Source: https://github.com/speakeasy-api/skills/tree/main/skills/orchestrate-multi-repo-sdks
Command: npx skills add https://github.com/speakeasy-api/skills --skill orchestrate-multi-repo-sdks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates cross-repo SDK generation and PR workflows when each language SDK lives in its own repository, removing the manual coordination burden.

Core Features & Use Cases

  • Cross-repo orchestration: Dispatch SDK generation across multiple language repositories from a single spec PR.
  • PR status reporting: Aggregate and post PR statuses back to the spec PR to keep stakeholders informed.
  • PR reconciliation on merge/close: Automatically reconcile or close SDK PRs when the spec PR is merged or closed.
  • Triggers & workflows: Responds to phrases like "multi-repo SDK", "cross-repo workflows", and "spec repo triggers SDK repos" to kick off coordinated actions.

Quick Start

In your spec repository, run the orchestrate-multi-repo-sdks skill to initialize cross-repo orchestration and connect language SDK repositories. Example: speakeasy run -y orchestrate-multi-repo-sdks

Frequently Asked Questions about orchestrate-multi-repo-sdks

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

FAQPage Schema
How do I trigger SDK generation across multiple repositories from a single spec PR?

Cross-repo SDK generation is triggered from a single spec PR by dispatching configured workflows to each language SDK repository, eliminating manual coordination. The orchestrate-multi-repo-sdks skill responds to spec repo activity to kick off coordinated actions across separate repositories.

How does cross-repo PR status reporting work for multi-repo SDK setups?

Cross-repo PR status reporting aggregates statuses from each language SDK repository and posts them back to the original spec PR. This keeps stakeholders informed about the generation and PR workflows across all separate repositories without manual checks.

Can I automatically reconcile or close SDK PRs when the spec PR is merged or closed?

PR reconciliation on merge or close is handled automatically via configured repository hooks. When the spec PR is merged or closed, the skill automatically reconciles or closes the corresponding SDK PRs across the separate language repositories.

What do I need to set up before orchestrating multi-repo SDK workflows?

You need a spec repository and separate language SDK repositories with configured workflows and repository hooks. Run the orchestrate-multi-repo-sdks skill in your spec repository to initialize cross-repo orchestration and connect the language SDK repositories.

When do I need cross-repo orchestration for SDK generation instead of a monorepo setup?

Cross-repo orchestration is needed when each language SDK lives in its own separate repository rather than a monorepo. It removes the manual coordination burden of triggering generation, reporting PR status, and reconciling PRs across these distinct repositories based on spec PR activity.