seed-changeset

Detects changed public packages in Git diffs and writes approved Korean changeset files.

1.1k|89|Updated Mar 11, 2021
One-click install
npx skills add https://github.com/daangn/seed-design --skill seed-changeset
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: seed-changeset
Source: https://github.com/daangn/seed-design/tree/main/skills/seed-changeset
Command: npx skills add https://github.com/daangn/seed-design --skill seed-changeset

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

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.

Frequently Asked Questions about seed-changeset

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create changesets for a monorepo release?

Run the changeset plan script with Bun against a base ref like origin/dev to list changed public packages and existing coverage. Then confirm a SemVer bump per package and approve the drafted Korean message before any .changeset markdown file is written.

How do I decide between major, minor, and patch bumps?

Classify by public output impact: breaking API, type, or render changes are major; backward-compatible features are minor; bug fixes restoring intended behavior are patch. The version-matrix reference covers CSS, React, Lynx, and Headless propagation rules.

Does this skill modify peer dependency ranges?

No. The skill never edits dependency or peer dependency ranges in package.json. Peer dependency lower-bound adjustments are flagged as review candidates and handled manually in a separate Version Changes PR.

Which packages are excluded from changeset candidates?

Private workspace packages and anything under packages/archive/* are excluded and reported with their exclusion reasons. Registry snippet-only changes also produce no changeset since snippets are copied code, not npm packages.

What Git base refs are supported by the plan script?

The CLI accepts only origin/dev, origin/minor, or origin/major as the base ref. Other refs such as HEAD are rejected with an error, and the script merges committed, staged, worktree, and untracked changes into one plan.

Why does the skill not write changeset files automatically?

The script is read-only and never infers change meaning or bump levels on its own. Files are written only after the user explicitly approves the per-package bumps and the drafted Korean messages.