Menú
Create and apply a prerelease bump using Changesets CLI, with the new changeset markdown summarizing the actual changes since the last shipped release.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when designing or refining event-sourced aggregates, commands, events, invariants, source-generator hooks, or snapshot-queryable mirror properties.
Use when defining event-sourced aggregate validation at command time, hook time, save time, or for computed snapshot/query mirror properties.
Use when modeling scalar, complex, or contextual value objects with source-generated normalization, validation, Hydrate/Create semantics, or query-translation awareness.
Use .NET with TUnit-specific test conventions.
Git workflow and conventional commit guidance.
Lefthook Git hook integration.
| 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 this repository.
npx @changesets/cli add --empty --message "<summary>".changeset/*.md frontmatter with:
"purview-eventsourcing": patch.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.npx @changesets/cli versionpackage.json, CHANGELOG.md, and consumed .changeset files)..changeset/*.md bodyPrepare next prerelease unless there were truly no meaningful changes.tag: prerelease (.changeset/pre.json).package.json version in the release.yml workflow.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.