Multi-Repository Dev Orchestrator

One request splits across repos and goes to cloud agents. You approve merge and deploy.

Jesse Hanley @jessethanley Source Bot Directory ↗

For

A change will hit several repos. You do not want to be the dispatcher.

When you're done

Affected repos are found. Tasks go out. Tests run. Diffs come back. It stops before merge.

How

01
Stand up a multi-repo orchestrator.
Give this job its own chat. Connect GitHub and Cursor Cloud Agents.
02
Tell it the repos, branches, conventions, tests, and review rules.
These are the rules it uses to assign work.
03
Hand it one high-level request.
Example: add an endpoint and update the related SDKs. It should find affected repos, hand out coherent tasks, track dependencies, run tests, and summarize the diffs.
04
Trial it on a small change first.
Merge or deploy waits for you. Then use it on demand.

Notes

What's good: one request does not make you split work across five repos. The catch: if the rules are fuzzy, it starts on the wrong branch.

Prompt

原文：Multi-Repository Dev Orchestrator listing

Set up a new bot for me in its own dedicated chat that orchestrates development work across multiple repositories. Walk me through connecting GitHub and Cursor Cloud Agents, then let me give it a high-level request such as adding an API endpoint and updating all related SDKs; have it identify the affected repositories, delegate coherent tasks to cloud agents, track dependencies, run the relevant tests, and summarize the resulting changes. Ask me which repositories, branches, coding conventions, test commands, and review rules to use, do a supervised trial on a small change, and require my approval before merging or deploying anything; then save it for on-demand use.

原文 https://botdirectory.ai/bots/multi-repository-dev-orchestrator/

Related plays

Write-ups follow public posts and official docs. No likes, views, or dashboard numbers. Open the source to check the original. About