Menu
Create and apply a prerelease bump using Changesets CLI, with the new changeset markdown summarizing the actual changes since the last shipped release.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when converting an Aspire AppHost (typically Program.cs/AppHost.cs) into Purview.Aspire.ResourceKit patterns: generate a HostKit, split resources into ResourceKits with BuildResource/ConfigureResource, map existing config into generated options (IsEnabled/Name), replace direct wiring with AddAspireResourceKit, and update tests/fixtures/configuration to use OptionsHelper and ResourceKit semantics.
Use when creating, moving, or splitting projects in a repository that uses Purview.DotNetProjectSdk, especially for src/tests placement, test suffix naming, namespace alignment, and automatic project-reference behavior.
Use when creating or refactoring .NET tests with TUnit conventions (AAA pattern, naming, async assertions, and CancellationToken usage).
Git workflow and conventional commit guidance.
Lefthook Git hook integration.
Use for quick TUnit --treenode-filter patterns.
| name | changesets-prerelease |
| description | Create and apply a prerelease bump using Changesets CLI, with the new changeset markdown summarizing the actual changes since the last shipped release. |
Use this skill when preparing the next prerelease version in a project that uses Changesets.
Add a new changeset:
npx @changesets/cli add --empty --message "<summary>".changeset/*.md frontmatter with the correct target package and bump type used by the repository..24) has not been released yet and you are preparing .25, the new markdown should still describe the cumulative changes that matter for the next published prerelease.Bump versions/changelog:
npx @changesets/cli versionCommit the resulting changes (package.json, CHANGELOG.md, and consumed .changeset files).
.changeset/*.md bodyPrepare next prerelease unless there were truly no meaningful changes..changeset/pre.json for the active prerelease tag.changeset version can record a changeset in .changeset/pre.json even if the new file was created with placeholder/empty content first. If that happens, correct the .md frontmatter/body before finalizing the release notes so the next shipped prerelease entry is accurate.