Stats
Actions
Tags
From dstack
Cross-repo dependency awareness, sync protocol, and build order for multi-repo work
How this skill is triggered — by the user, by Claude, or both
Slash command
/dstack:multi-repo-opsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use when work touches 2+ repos in the tracked list.
Use when work touches 2+ repos in the tracked list.
dstack sync --status
Shows branch, clean/dirty, ahead/behind for every tracked repo.
# Dry run first
dstack sync --dry-run
# Pull + push all clean repos
dstack sync
Only syncs repos with clean working trees. Dirty repos are skipped with a warning.
When changes span repos, build in dependency order:
Example order:
core-lib → api-server → client-app
memory-engine → mcp-bridge
cli-tool (standalone)
Before committing cross-repo changes:
Some projects use feature branches or non-default branches. Check dstack sync --status to see which branch each repo is on. Don't mix — if repo A is on a feature branch, keep it there.
Tracked repos are set in ~/.config/dstack/config.toml:
[repos]
tracked = ["my-api", "my-lib", "my-frontend"]
npx claudepluginhub dirmacs/dstack --plugin dstackCoordinates changes across multiple repositories by syncing skills, templates, agents, and harness policies via git-mediated workflows or specification-mediated patterns for multi-repo projects.
Coordinates multi-repo campaigns across repositories with shared context: decomposition into repo-scoped work items, wave execution, cross-repo contracts, and session tracking.
Coordinates multi-repo swarms, synchronizes packages, and optimizes repository architecture across GitHub organizations. Use when changes span several repos or planning cross-repo work.