What problem does it solve?
Releasing a monorepo requires deciding which packages changed, what SemVer bump each deserves, and writing consistent changeset files. Doing this by hand across many workspace packages is error-prone and often produces duplicate or missing changesets.
Core Features & Use Cases
- Read-only release planning: Runs a Bun script that scans the Git diff against a base ref (origin/dev, origin/minor, origin/major) and reports changed public packages, existing changeset coverage, reverse dependencies, and peer dependency review candidates.
- SemVer bump classification: Uses a version matrix reference to classify each package's public API impact as major, minor, patch, or no release, including CSS-to-React and Headless-to-wrapper propagation rules.
- User-approved changeset authoring: Drafts Korean consumer-facing changeset messages following strict writing patterns, and only writes
.changeset/*.md files after the user approves the bumps and messages.
- Use Case: After finishing a feature branch in the SEED design system monorepo, run the plan script to see that
@seed-design/css and @seed-design/react changed, confirm a minor bump for each, and generate a single changeset file describing the new component in Korean.
Quick Start
Analyze my current Git changes against origin/dev and draft changeset files for the affected public packages.