seed-changeset

SEED Changeset

Find release candidates in the current diff, and decide the bump based on the impact on the public output. Do not automatically guess the meaning of changes or the bump. Only after the user approves the per-package bump and message, write .changeset/*.md.

This skill does not modify the dependency or peer dependency ranges of package.json. Adjusting the peer dependency lower bound required by a new feature is handled manually in the Version Changes PR.

Candidate plan

Run the read-only plan script from the repository root.

bun skills/seed-changeset/scripts/changeset-plan.ts --base-ref origin/dev

--base-refIn seed-change-plan, specify the actual base branch selected by targetRef. Before rebasing, use the feature branch's existing base. In the final check after rebasing, use the confirmed

. Check the following items in the results.

• candidates: Public workspace packages changed since the base branch. For renames, include both the old and new paths. Deleted packages are restored from the base branch's package.json.
• excluded: Packages excluded from changeset candidates because they are private or packages/archive/*.
• coveredBy: Shows whether the existing .changeset/*.mdalready covers the candidates. If there are sufficient files, do not create a duplicate changeset.
• reverseDependencies: Public workspace packages that depend on the change candidates. Use this when determining whether the actual public impact propagates.
• versionChangesReviewCandidates: A list of candidates for reviewing the peer dependency lower bound in the Version Changes PR. In the current task, do not modify the package.jsonin this list.

The script shows commits, index, worktree, and untracked files since the base branch combined. If stacked changes are mixed in, read the candidate diffs and commit logs directly and keep only the packages belonging to this task.

Bump confirmation

version-matrix.md. Directly check each candidate's public exports, types, props, Recipes, tokens, render results, and accessibility behavior, and recommend one of major, minor, patch, 안함(제외) .

Apply standard SemVer equally to all packages. For Lynx packages too, breaking is major, backward-compatible feature additions are minor, and bug fixes are patch다.

Reverse-dependency packages become companion bump candidates only when they actually consume the new feature or expose the change on their public surface. Do not create a companion bump just because a dependency relationship exists. This judgment is for determining the changeset scope and does not permit editing dependency ranges.

Show the recommended bump and rationale for each package to the user and get confirmation. The script does not decide the meaning of changes, the bump, or the distribution branch.

Message writing and approval

patterns.mdRead and write a Korean message from the perspective of a design system consumer. When a single user change propagates to multiple packages, bundle them into one file. Separate independent changes into different files.

Show the draft in the following format.

## Changeset 초안

| 패키지 | bump |
| --- | --- |
| @seed-design/react | patch |

```changeset
---
"@seed-design/react": patch
---

사용자에게 보이는 변경을 설명합니다.
```

Do not write files until the user approves the bump and message. If there is a revision request, show the revised draft again.

File creation and verification

After approval, .changeset/<형용사-명사-동사>.mdcreate a new one. Use three lowercase English words that do not conflict with existing filenames. Wrap the frontmatter package name in double quotes. Do not overwrite existing files.

Run the planning script again with the same baseRefto check coverage. Among versionChangesReviewCandidates , leave actual new feature consumers as a Version Changes PR follow-up item in the final report. Do not edit the peer range in this task.

Pass the highest confirmed bump as the basis for the branch decision in the final seed-change-plan. This skill does not perform rebase, commit, push, PR creation, or deployment.