multi-repo-workspace

Coordinate changes across multiple repositories in a single workspace.

Updated Jan 21, 2026

Search Tags:#collaboration #orchestration #workspace #monorepo #multi-repo #dependency-graph #coordinate

Ready to run

npx skills add https://github.com/jairoFernandez/llm-skills --skill multi-repo-workspace

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: multi-repo-workspace
Source: https://github.com/jairoFernandez/llm-skills/tree/main/skills/multi-repo-workspace
Command: npx skills add https://github.com/jairoFernandez/llm-skills --skill multi-repo-workspace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating changes across many repositories within a single workspace to preserve consistency, reduce drift, and streamline multi-repo deployments.

Core Features & Use Cases

Centralized inventory with per-repo context and automatic dependency tracking
Automatic repository type detection across frontend, backend, mobile, devops, and shared repos
Coordinated multi-repo tasks with cross-repo orchestration and change coordination
Real-world use case: implementing a cross-cutting feature (e.g., authentication) across client, API gateway, and services with synchronized updates

Quick Start

Install the skill into Claude Projects or via custom instructions, then run:

@workspace init my-workspace
@workspace add ./frontend ./backend ./shared
@workspace analyze

Frequently Asked Questions about multi-repo-workspace

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

FAQPage Schema

How do I coordinate changes across multiple repositories in a single 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.

Does multi-repo workspace orchestration support both monorepos and microservices?▼

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.

How do I generate a dependency graph for multiple repositories?▼

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.

What is the best way to implement a cross-cutting feature like authentication across client, API gateway, and services?▼

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.

Do I need per-repo configuration files to use multi-repo workspace coordination?▼

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.

When should I not use a multi-repo workspace for coordinating changes?▼

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.