skills.rest
mpsuesser
mpsuesserCOMMUNITY
Explore all skills by this author →
GitHub

changesets

Add, validate, and use Changesets to generate semantic version bumps and changelog entries.

Updated Mar 12, 2026
Search Tags:#semantic versioning#npm publish#CI checks#changesets#changelog generation#monorepo releases
One-click install
npx skills add https://github.com/mpsuesser/workspace --skill changesets-mpsuesser
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changesets
Source: https://github.com/mpsuesser/workspace/tree/main/dotconfig/pi/agent/skills/__techs__/changesets
Command: npx skills add https://github.com/mpsuesser/workspace --skill changesets-mpsuesser

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Changesets helps teams consistently capture what changed, at what semantic version level, and how that should appear in package changelogs—especially in monorepos.

Core Features & Use Cases

  • Add change intent (with semver bump types): Create a changeset file describing which packages to release and whether each is major, minor, or patch.
  • Generate versions and changelogs: Run the version step to apply accumulated changesets into updated package versions and release notes.
  • Publish and manage release tags: Publish updated packages to npm and create/push git tags, optionally supporting snapshot or prerelease workflows.
  • Use CI-friendly checks: Use status/since checks (and bots) to detect missing changesets before releases.

Quick Start

Use the changesets workflow to add a changeset for your branch and then run the release steps when you are ready.

Frequently Asked Questions about changesets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate changelogs and semantic version bumps for a monorepo?▼

To generate changelogs and semantic version bumps for a monorepo, add a changeset file declaring which packages to release and the semver level, then run the version step to apply accumulated changesets into updated package versions and release notes.

What is a changeset and when do I need to create one?▼

A changeset is a file that records release intent by describing which packages to release and whether each requires a major, minor, or patch bump. You create one whenever you need to capture what changed for future changelog generation.

How do I publish updated packages to npm and manage git tags?▼

Publish updated packages to npm and manage git tags by running the release steps after generating versions. This publishes your packages and creates or pushes git tags, with options for snapshot or prerelease workflows.

Can I use CI checks to detect missing changesets before a release?▼

Yes, you can use CI-friendly status and since checks to detect missing changesets before releases. These checks integrate with bots to ensure contributors record release intent and maintain consistent version updates across packages.

Does this changesets workflow apply to single-package repositories or only monorepos?▼

The changesets workflow applies to both monorepos and single-package repositories. It guides contributors to record release intent and maintain consistent dependency and version updates across one or many packages.

Related Skills

Explore More Software Engineering Skills→
INNERJOINTINNERJOINT

release

Automate version bumps, tests, npm publishing, and GitHub releases.

Community
Advanced
tneztnez

release-package

Create and publish new npm package versions with changelog updates.

Community
Intermediate
OpenSaasAUOpenSaasAU
2

pr-changeset

Generate changeset files for package changes in a monorepo.

Official
Intermediate
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate