What problem does it solve?
This Skill provides a concise, actionable map of GROWI's monorepo layout, workspace orchestration, and release practices so developers can correctly add, build, and version packages without breaking dependent workspaces or CI pipelines.
Core Features & Use Cases
- Repository topology: Explains the apps/ and packages/ layout, key shared packages (for example @growi/core and @growi/pluginkit), and where configuration files like pnpm-workspace.yaml and turbo.json live.
- Workspace & build orchestration: Details pnpm workspace usage, Turborepo task orchestration, explicit per-package turbo.json patterns for build-order, and when to update dependencies to avoid missing dist artifacts.
- Release and versioning workflow: Describes the Changesets workflow for shared libraries and the separate versioning policies for the main app and microservices.
- Use case: When adding a new package that depends on @growi/core, use this Skill to determine what workspace references, turbo.json dependsOn entries, and changeset steps are required to build, test, and release safely.
Quick Start
Use the monorepo-overview skill to summarize the build-order and workspace dependency changes required when a package adds a new dependency on @growi/core.