multi-repo-workspace

Multi-repo workspace coordination is achieved by initializing a workspace, adding local repository paths, and analyzing them to automatically detect repo types, read per-repo context files, and build a dependency graph for synchronized cross-repo updates.

Yes, multi-repo workspace orchestration supports monorepos, microservices, and other multi-repo projects by automatically detecting repository types across frontend, backend, mobile, devops, and shared repos to maintain cross-repo consistency.

To generate a dependency graph for multiple repositories, run an analyze command on your initialized workspace to read per-repo context.md and config.json files, automatically mapping dependencies and suggesting execution orders and integration points.

The best way to implement a cross-cutting feature like authentication across client, API gateway, and services is using multi-repo workspace orchestration to coordinate synchronized updates and execute tasks across all affected repositories within a single workspace.

Yes, multi-repo workspace coordination reads per-repo .claude/config.json and context.md files to extract repository context, which is used to build the dependency graph and suggest execution orders for coordinated task execution.

You should avoid multi-repo workspace coordination if your project lacks per-repo context files, does not involve cross-repo dependencies, or operates as an isolated single repository without the need for synchronized multi-repo deployments or dependency graph tracking.