Write Change Set
Use this skill when the user wants the PR or branch to carry a changeset before merge.
First Checks
- Read repo instructions such as
AGENTS.md, CLAUDE.md, and release docs.
- Detect existing workflow files:
.changeset/, CHANGELOG.md, package scripts, release scripts, PR template, and tests.
- Inspect the branch or PR diff before writing anything.
- If the workflow already exists, follow the repo's local commands and file format.
Normal Workflow
- Find an existing branch-local
.changeset/*.md file. Update it when it belongs to this PR.
- If none exists and the PR needs one, create exactly one pending changeset file.
- Choose the smallest defensible type:
major, minor, or patch.
- Choose the changelog category used by the repo, usually
Added, Changed, Deprecated, Removed, Fixed, Security, Migration Notes, App Author Notes, Known Issues, or Upgrade Notes.
- Write the note in user-facing language describing the final result of the PR.
- Run the repo's changeset validation command, such as
pnpm changeset:check-pr.
Boundaries
- Do not edit
CHANGELOG.md.
- Do not bump versions.
- Do not move files into
.changeset/released/.
- Do not create tags, pushes, or GitHub Releases.
- If the PR does not need a changeset, say that directly and explain the reason.
Missing Workflow
If the repo does not have a changeset workflow, stop and tell the user to install it with
the setup-release-kit skill. That skill owns the canonical scripts, CI gate, and release
tooling; this skill only writes notes into an installed workflow. Do not scaffold from here.
References
- For file format rules, read
references/changeset-format.md.
- For prompt and output examples, read
references/examples.md.
1---2name: write-changeset3description: Write or update a change set (changeset) file for a pull request or branch. Use when the user says to write, add, update, or run the change set or changeset for a PR/branch before merge. If the repo has no changeset workflow, install it with setup-release-kit first.4license: MIT5---67# Write Change Set89Use this skill when the user wants the PR or branch to carry a changeset before merge.1011## First Checks12131. Read repo instructions such as `AGENTS.md`, `CLAUDE.md`, and release docs.142. Detect existing workflow files: `.changeset/`, `CHANGELOG.md`, package scripts, release scripts, PR template, and tests.153. Inspect the branch or PR diff before writing anything.164. If the workflow already exists, follow the repo's local commands and file format.1718## Normal Workflow19201. Find an existing branch-local `.changeset/*.md` file. Update it when it belongs to this PR.212. If none exists and the PR needs one, create exactly one pending changeset file.223. Choose the smallest defensible type: `major`, `minor`, or `patch`.234. Choose the changelog category used by the repo, usually `Added`, `Changed`, `Deprecated`, `Removed`, `Fixed`, `Security`, `Migration Notes`, `App Author Notes`, `Known Issues`, or `Upgrade Notes`.245. Write the note in user-facing language describing the final result of the PR.256. Run the repo's changeset validation command, such as `pnpm changeset:check-pr`.2627## Boundaries2829- Do not edit `CHANGELOG.md`.30- Do not bump versions.31- Do not move files into `.changeset/released/`.32- Do not create tags, pushes, or GitHub Releases.33- If the PR does not need a changeset, say that directly and explain the reason.3435## Missing Workflow3637If the repo does not have a changeset workflow, stop and tell the user to install it with38the `setup-release-kit` skill. That skill owns the canonical scripts, CI gate, and release39tooling; this skill only writes notes into an installed workflow. Do not scaffold from here.4041## References4243- For file format rules, read `references/changeset-format.md`.44- For prompt and output examples, read `references/examples.md`.
brandtam