Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From groundwork
Detects single-project or monorepo structure, creates .groundwork.yml config for monorepos, updates .gitignore, and persists project selection for Groundwork.
npx claudepluginhub etr/groundworkHow this skill is triggered — by the user, by Claude, or both
Slash command
/groundwork:repo-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this 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.
Initializes and configures projects: detects tech stacks, scaffolds new apps, creates task files, sets branch strategies, handles git submodules, exports to other AI platforms.
Bootstraps new projects or improves existing ones with best practices for structure, git, documentation, testing, code quality, dependencies, dev workflow, and CI/CD.
Initializes new Python, Rust, or TypeScript projects interactively with git repo, GitHub workflows, pre-commit hooks, Makefile, and standard configs. Updates existing projects too.
Share bugs, ideas, or general feedback.
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.
Look for common monorepo patterns:
package.json, go.mod, Cargo.toml, etc.apps/, packages/, services/, projects/specs/ directory (suggests single-project)pnpm-workspace.yaml, lerna.json, turbo.json)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."
If single project:
.groundwork-plans/ is in .gitignore (add it if missing) — execute-task writes per-task plan files there.specs/ at the repo root.".groundwork.yml created.If monorepo:
AskUserQuestion with multi-select to confirm project list..groundwork.yml:version: 1
projects:
<project-name>:
path: <relative/path>
<project-name>:
path: <relative/path>
.groundwork.local and .groundwork-plans/ are in .gitignore (add any missing entries). .groundwork-plans/ is where execute-task writes per-task plan files.AskUserQuestion.GROUNDWORK_PROJECT=<name> and GROUNDWORK_PROJECT_ROOT=<path>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/."
This skill can also be invoked to add or remove projects from an existing .groundwork.yml:
| 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 |