orchestrate-multi-repo-sdks

Orchestrate SDK generation and PR management across multiple repositories.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/berea-ch/bereach-sdk-ts --skill orchestrate-multi-repo-sdks-berea-ch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrate-multi-repo-sdks
Source: https://github.com/berea-ch/bereach-sdk-ts/tree/main/.agents/skills/orchestrate-multi-repo-sdks
Command: npx skills add https://github.com/berea-ch/bereach-sdk-ts --skill orchestrate-multi-repo-sdks-berea-ch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the management of multiple SDK repositories, ensuring consistency and automating cross-repository workflows triggered by changes in a central API specification repository.

Core Features & Use Cases

  • Cross-Repository Workflow Triggering: Automatically initiates SDK generation in individual language SDK repositories when changes occur in the API specification repository.
  • PR Synchronization: Manages Pull Requests across SDK repositories, automatically merging or closing them based on the status of the corresponding PR in the spec repository.
  • Use Case: When a new API endpoint is added to the main spec, this Skill ensures that the TypeScript, Python, and Go SDKs are automatically updated in their respective repositories, with new PRs created for each.

Quick Start

Use the orchestrate-multi-repo-sdks skill to synchronize SDK repositories when a pull request is opened in the main API specification repository.

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 automate SDK generation across multiple repositories when an API spec changes?

SDK generation is automated across multiple separate SDK repositories by dispatching cross-repository workflows whenever changes occur in a central API specification repository. It triggers individual SDK generation pipelines and manages the resulting pull requests automatically.

Can I synchronize pull requests across separate SDK repositories with GitHub Actions?

Pull request synchronization across SDK repositories is managed by automatically merging or closing language-specific SDK PRs based on the status of the corresponding pull request in the central API specification repository.

What's the best way to manage cross-repo CI/CD workflows for SDK updates?

Cross-repo CI/CD workflows for SDK updates are managed by orchestrating workflow dispatches to individual language repositories. It handles PR status reporting and reconciles pull requests on merge or close events from the spec repository.

Do I need GitHub CLI and Speakeasy CLI to orchestrate multi-repo SDK workflows?

GitHub CLI and Speakeasy CLI are required for execution to orchestrate multi-repo SDK workflows. These tools enable the automation to dispatch cross-repository workflows, generate SDKs, and manage pull request reconciliation.

When a pull request is opened in the API specification repository, how are language SDKs updated?

When a pull request is opened in the API specification repository, cross-repository workflows are triggered to initiate SDK generation in individual language repositories. New pull requests are created for each separate SDK repository to propose the updates.