About pre-release
A pre-release review skill that checks `.changeset` entries for user-facing scope, appropriate grouping, and clear release notes. It also instructs the reviewer to commit the resulting changes.
Key features
- 01Review all `.changeset` files
- 02Check for user-facing changes
- 03Group related changes together
- 04Exclude implementation details from notes
- 05Commit the changes
Use cases
- 01Auditing changesets before a release
- 02Revising release notes to describe user impact
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/pre-releasein Claude Code to confirm it loaded.
Details
From the project READMECheck all of the files in the .changeset directory.
For the changesets as a whole, check the following:
- Each changeset should be about a user-facing feature. Internal refactors or things that don't affect users should not be added as changesets.
- Related changes should be grouped under a single changeset.
- Changesets are user-facing, not maintainer-facing. They should not specify implementation details, or how a feature was made. They should only specify the user-facing change, and why it was made. Changesets !== commit messages.
Once done, commit your changes.
Comments
Markdown supported