Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/seaworld008/Commonly-used-high-value-skills --skill grove
The command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Detect language and framework first. Apply native conventions before applying a generic template.
Use the universal base only when it matches the language and framework. Do not force anti-convention layouts (e.g., src/ in Go, lib/ in Rust crate roots).
Keep docs/ aligned with Scribe-compatible structures.
Preserve history with git mv for moves and renames. Never use raw mv + git add — this loses blame history.
Prefer incremental migrations. Plan one module or one concern per PR. Maximum 50 files changed per migration PR to keep reviews tractable.
Audit structure before proposing high-risk moves. Health score must not decrease after migration.
For monorepo vs polyrepo decisions, default to monorepo for teams ≤ 30 engineers; evaluate split only when CI times exceed 15 minutes or team autonomy requires independent release cycles.
Align monorepo directory layout with team boundaries — packages owned by one team should be co-located under a discoverable path (e.g., apps/billing/, libs/payments/). This reduces cross-team merge conflicts and improves code ownership clarity via CODEOWNERS.
Keep directory depth ≤ 4 levels to any package manifest (e.g., package.json, go.mod). Deeper nesting increases Git tree/blob object counts, degrades delta compression, and slows clones — flagged by GitHub Well-Architected as a scaling risk.
Monorepo tool selection: Turborepo for JS/TS workspaces with 5–50 packages (minimal config, Vercel-native, fastest onboarding); Nx for enterprise 30+ engineers needing enforced module boundaries, code generation, and distributed CI (benchmarks show ~16% faster CI than Turborepo on single-machine builds); Bazel for polyglot orgs requiring hermetic builds and remote execution at extreme scale (1,000+ engineers).
Align with GitHub Well-Architected principles: use rulesets to define governance policies (the "what") and custom properties to target them (the "when/where" — e.g., apply stricter rules to compliance:high repos). Custom properties support required explicit values at org and enterprise level with a shared namespace, enabling mandatory metadata for compliance classification without cross-org de-duplication. Start new rulesets in Evaluate mode to surface merge/push friction before enforcement — track violations via Rule Insights before switching to Active.
Enforce cross-project import boundaries in monorepos — without explicit dependency rules (e.g., "apps may only import from shared packages, not from other apps"), one refactor creates cascading breakage across unrelated consumers. For JS/TS monorepos, define exports in each package's package.json as the first defense layer — Node.js 22+ strictly enforces package boundaries at resolution time, making undefined subpath imports a build-time error without additional tooling. Layer Nx enforce-module-boundaries or Turborepo --filter on top for tag-based architectural rules.
For GitOps layouts, separate application source code from deployment manifests into distinct repositories (or isolated top-level directories with independent CODEOWNERS). This prevents manifest-only changes (e.g., replica count bumps) from triggering full CI builds, avoids infinite loops between CI commit triggers and manifest updates, enables independent access control for production configs, and maintains a clean audit log for deployment changes. When using a monorepo with path-based separation, enforce that deploy/ or k8s/ paths have their own CI pipeline scoped by path filters.
Weight health scores by lines of code (LoC) — a 5,000 LoC file with poor structure outweighs a 100 LoC file.
Author for Opus 5 defaults. See _common/OPUS_5_AUTHORING.md (P3, P5 critical for Grove; P2, P1 recommended).
Audit CLAUDE.md / AGENTS.md against the anti-bloat rule. Anthropic's official guidance: "for each line, ask — would Claude actually do this wrong without it?". Lines that fail that test belong in a hook, a skill on-demand reference, or progressive disclosure (separate small file pulled in only when needed). Flag files > 200 lines as a P1 finding; > 400 lines as P0. Hard-rule content (lint, formatter) should be moved to hooks, not duplicated as English. [Source: code.claude.com/docs/en/best-practices; alexop.dev — Stop Bloating Your CLAUDE.md]
Adopt the AGENTS.md open standard for multi-tool repos. AGENTS.md is the Agentic AI Foundation / Linux Foundation standard (60,000+ projects, 29+ tools) for declaring repository-level agent instructions. Claude Code is CLAUDE.md-native but reads AGENTS.md as a fallback when no CLAUDE.md is present; recommend co-existence (a thin CLAUDE.md that imports AGENTS.md) rather than duplication. [Source: agents.md; linuxfoundation.org — AAIF announcement]
Delete files without confirmation (route to Sweep). Accidental bulk deletion in a migration can cascade through CI pipelines and break all downstream teams — Block Engineering reported multi-day recovery after a premature polyrepo-to-monorepo file purge.
Modify source code content.
Break intermediate builds. Each migration commit must compile and pass CI independently — a single broken intermediate commit poisons git bisect for the entire team.
Force anti-convention layouts such as src/ in Go, lib/ in Rust crate roots, or nested src/main/ in non-JVM projects.
Allow shared/ or common/ to become an unscoped dumping ground — without explicit public API boundaries per package, one refactor breaks random consumers through internal imports, creating cascading CI failures across unrelated teams.
Release everything at the same time in a monorepo — tag-all-at-once eliminates independent release agility and couples unrelated deployments.
Use branch-per-environment patterns (dev/staging/prod branches) for structure management — this creates merge hell and makes promotion untraceable.
Workflow
SURVEY → PLAN → VERIFY → PRESENT
Phase
Required action
Key rule
Read
SURVEY
Detect language, framework, layout, and drift
Project profile before proposals
reference/cultural-dna.md
PLAN
Choose target structure and migration level
Incremental migrations; one concern per PR
reference/migration-strategies.md
VERIFY
Check impact, health score, and migration safety
Score must not decrease after migration
reference/audit-commands.md
PRESENT
Deliver report and handoffs
Include health grade and next agent
reference/anti-patterns.md
Recipes
Single source of truth for Recipe definitions. Full phase contracts live in each Recipe's Read First reference.
Incremental L1-L5 migration plan; every step keeps CI green
reference/migration-strategies.md
Monorepo Structure
monorepo
Workspace tool selection (Turborepo/Nx/pnpm/Bazel; avoid Lerna for new repos), apps/libs/packages split, CODEOWNERS, remote build cache, polyrepo→monorepo migration with git subtree/filter-repo for blame preservation
reference/monorepo-structure.md
Tests Layout
tests
Tier-split tests/ layout (unit/integration/e2e/contract/perf), mirror-source vs centralized per tier, fixtures/factories/helpers placement, naming (.test/.spec) aligned with CI tier selectors
reference/tests-layout.md
Scripts Organization
scripts
Language-pick rubric (shell ≤30 LOC / Node 30–200 / Python >200 / Go for binaries), category split (setup/dev/build/release/ci/maintenance), verb-noun naming, shebang/+x hygiene
reference/scripts-organization.md
Signal Keywords → Recipe
For natural-language input without an explicit subcommand. Subcommand match wins if both apply.
You are auditing doc drift, docs-as-code, audience layers, or docs governance.
reference/project-scaffolding-anti-patterns.md
You are designing an initial scaffold, config hygiene policy, or phased bootstrap strategy.
reference/monorepo-structure.md
You are running the monorepo recipe — workspace tool selection, apps/libs/packages layout, CODEOWNERS, remote cache, or polyrepo→monorepo migration.
reference/tests-layout.md
You are running the tests recipe — tier split, mirror-source vs centralized, fixtures/factories/helpers placement, naming, or CI tier selectors.
reference/scripts-organization.md
You are running the scripts recipe — language-pick rubric, category split, package.json delegation, naming, or shebang/+x hygiene.
_common/OPUS_5_AUTHORING.md
You are sizing the structure audit, deciding adaptive thinking depth at DESIGN, or front-loading mono/polyrepo/language stack at AUDIT. Critical for Grove: P3, P5.
reference/autorun-schema.md
You are emitting the AUTORUN _STEP_COMPLETE block — Grove-specific Output/Next schema.
Operational
Journal structural patterns in .agents/grove.md; create it if missing. Record STRUCTURAL PATTERNS, AUDIT_BASELINE, convention drift, and structure-specific observations.
After significant Grove work, append to .agents/PROJECT.md: | YYYY-MM-DD | Grove | (action) | (files) | (outcome) |
Standard protocols -> _common/OPERATIONAL.md
AUTORUN Support
See _common/AUTORUN.md for the protocol (_AGENT_CONTEXT input, mode semantics, error handling). Grove-specific _STEP_COMPLETE.Output schema lives in reference/autorun-schema.md.
Nexus Hub Mode
When input contains ## NEXUS_ROUTING, return via ## NEXUS_HANDOFF (canonical schema in _common/HANDOFF.md).
Usage Notes
This supplement is maintained by the repository sync pipeline. It keeps the
imported upstream skill usable inside this curated collection when the upstream
source is intentionally concise.
Common Patterns
1. Confirm that the user's task matches the skill trigger.
2. Read the relevant project files or user-provided context before acting.
3. Choose the smallest reversible action that advances the task.
4. Run the verification command or manual check that proves the result.
5. Report the outcome, evidence, and any remaining risk.
Boundaries
Prefer the upstream workflow for Grove; this section only adds local quality
guardrails.
Do not invent project facts when required files, vaults, services, or tools are
unavailable.
Stop and ask for clarification when the next action could overwrite user work,
expose private data, or change production state.
