umbrella-repo-detector

Detect multi-repo architectures and generate project-scoped user stories.

156|21|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/anton-abyzov/specweave --skill umbrella-repo-detector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: umbrella-repo-detector
Source: https://github.com/anton-abyzov/specweave/tree/main/plugins/specweave/skills/umbrella-repo-detector
Command: npx skills add https://github.com/anton-abyzov/specweave --skill umbrella-repo-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and guides setup for umbrella/multi-repo architectures (frontend/backend/shared), and prefixes user stories for cross-repo coordination.

Core Features & Use Cases

  • Multi-repo detection for FE/BE/Shared patterns
  • Project-scoped user stories (US-FE-, US-BE-, US-SHARED-*)
  • Setup guidance for per-repo configuration and syncing

Quick Start

If you describe a 3-repo frontend/backend/shared setup, the tool generates repository structure and starter SW config.

Frequently Asked Questions about umbrella-repo-detector

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

FAQPage Schema
How do I detect and set up a multi-repo architecture with frontend, backend, and shared code?

Multi-repo detection identifies your frontend/backend/shared division from project descriptions and generates structured setup guidance. The tool analyzes your repository count and organization pattern, then produces repository-scoped user stories (US-FE-*, US-BE-*, US-SHARED-*) and configuration steps for umbrella repo coordination.

What's the difference between monorepo and multi-repo architectures, and when should I use each?

Monorepo consolidates multiple projects in one repository; multi-repo separates them. Multi-repo suits teams needing independent deployment cycles, frontend/backend autonomy, or shared library isolation. Detection patterns identify your current structure and guide migration or initial setup.

How do I organize shared code across multiple repositories?

Shared-repo organization centralizes common libraries and utilities accessible to frontend and backend repos. Setup guidance covers per-repo configuration, dependency syncing, and umbrella repo structure to coordinate version alignment and cross-repo updates across your architecture.

Can I use this for microservices or only frontend/backend splits?

Detection applies to multi-repo patterns including frontend/backend/shared divisions, microservices, and separate repository setups. The tool generates user stories and configuration guidance tailored to your specific repository count and division types.

What setup does the tool provide after detecting my repository structure?

After detection, the tool generates project-scoped user stories prefixed by repository type (US-FE-*, US-BE-*, US-SHARED-*), umbrella repo structure templates, and starter configuration guidance for per-repo setup and cross-repo synchronization.