Skill

repo-setup

Detects single-project or monorepo structure, creates .groundwork.yml config for monorepos, updates .gitignore, and persists project selection for Groundwork.

Git

git-workflow

automation

Install

npx claudepluginhub etr/groundwork

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Configures the repository structure for Groundwork. Detects or asks whether this is a single-project repo or a monorepo, and creates `.groundwork.yml` for monorepos.

SKILL.md

Similar Skills

kotlin-ktor-patterns

Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.

everything-claude-code

163.2k

deep-research

Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.

everything-claude-code

163.2k

inventory-demand-planning

Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.

everything-claude-code

163.2k

Stats

Stars37

Forks4

Last CommitApr 8, 2026

Actions

View Source View Plugin View on GitHub View README

Setup Repository Skill

Configures the repository structure for Groundwork. Detects or asks whether this is a single-project repo or a monorepo, and creates .groundwork.yml for monorepos.

Workflow

Step 1: Detect Repository Structure

Look for common monorepo patterns:

Multiple directories with their own package.json, go.mod, Cargo.toml, etc.
Common monorepo directories: apps/, packages/, services/, projects/
Existing specs/ directory (suggests single-project)
Workspace configuration files (pnpm-workspace.yaml, lerna.json, turbo.json)

Step 2: Ask User

Use AskUserQuestion to confirm:

"I've analyzed your repo structure. Is this:"

Single project — One project, specs at the repo root

Monorepo — Multiple projects, each with their own specs

If monorepo indicators were found, mention them:

"I noticed [apps/, packages/, workspace config], which suggests a monorepo structure."

Step 3: Configure

If single project:

No config file needed
Ensure .groundwork-plans/ is in .gitignore (add it if missing) — execute-task writes per-task plan files there.
Confirm: "Single-project mode. Specs will be stored in specs/ at the repo root."
Proceed — no .groundwork.yml created.

If monorepo:

Ask which directories are projects. Suggest based on detected structure.
Use AskUserQuestion with multi-select to confirm project list.
Create .groundwork.yml:

version: 1
projects:
  <project-name>:
    path: <relative/path>
  <project-name>:
    path: <relative/path>

Ensure .groundwork.local and .groundwork-plans/ are in .gitignore (add any missing entries). .groundwork-plans/ is where execute-task writes per-task plan files.
Ask which project to start with using AskUserQuestion.
Set project context: GROUNDWORK_PROJECT=<name> and GROUNDWORK_PROJECT_ROOT=<path>

Step 4: Persist Selection

For monorepo mode, persist the selection to .groundwork.local at the repo root (gitignored) so it survives session restarts.

Confirm: "Project selected. Specs will be stored in <path>/specs/."

Adding Projects Later

This skill can also be invoked to add or remove projects from an existing .groundwork.yml:

Read existing config
Present current projects
Ask what to add/remove
Update the config file

Edge Cases

Situation	Response
`.groundwork.yml` already exists	Show current config, ask if user wants to modify
No obvious project directories	Ask user to specify paths manually
User says single-project but monorepo indicators exist	Accept user's choice, note the indicators