repo-setup

Detect repository structure and generate a .groundwork.yml mapping projects in monorepos.

41|4|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/etr/groundwork --skill repo-setup-etr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-setup
Source: https://github.com/etr/groundwork/tree/main/skills/repo-setup
Command: npx skills add https://github.com/etr/groundwork --skill repo-setup-etr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configures the repository for Groundwork by detecting whether the repo is a single-project layout or a monorepo, and by preparing a .groundwork.yml to map projects when needed.

Core Features & Use Cases

  • Detects repo structure by scanning for common monorepo indicators (apps/, packages/, workspace configs, specs/).
  • Prompts the user to confirm single-project vs monorepo structure and to select project assignments.
  • Generates a .groundwork.yml with a list of projects and their paths for monorepos, and ensures .groundwork.local is gitignored for persistent context.
  • Supports adding or removing projects from an existing config and persists the selection for session continuity.

Quick Start

Analyze the repository structure and generate a .groundwork.yml with project mappings appropriate to single-project or monorepo setups.

Frequently Asked Questions about repo-setup

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

FAQPage Schema
How do I configure a monorepo for Groundwork project mapping?

Configuring a monorepo for Groundwork involves detecting workspace indicators, prompting for project assignments, and persisting the selections into a .groundwork.yml file that maps project paths for session continuity.

How does repo structure detection work for single-project versus monorepo setups?

Repo structure detection works by scanning for monorepo indicators like apps/, packages/, and workspace configs, then prompting you to confirm whether the repository is a single-project or multi-project monorepo layout.

Do I need to manually edit .gitignore when setting up Groundwork config files?

You do not need to manually edit .gitignore for Groundwork, because the setup process automatically ensures .groundwork.local is added to gitignore for persistent local context.

Can I add or remove projects from an existing .groundwork.yml config file?

You can add or remove projects from an existing .groundwork.yml config file, and the setup process will validate and persist your updated project selections for ongoing session continuity.

What is the best way to map projects in a monorepo with multiple workspace directories?

The best way to map projects in a monorepo with multiple workspace directories is to run the Groundwork setup, which detects specs/ and workspace configs, guides project selection, and writes paths to .groundwork.yml.

Why does my Groundwork setup require user confirmation during repo structure detection?

Groundwork setup requires user confirmation during repo structure detection to validate whether the repository is a single-project layout or a monorepo, ensuring the generated .groundwork.yml accurately maps the correct project paths.