skills.rest
yamcodes
yamcodesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

changeset

Creates changesets for semantic versioning and changelog generation in monorepos.

1|Updated Aug 24, 2026
Search Tags:#changelog#release management#semantic versioning#monorepo#changesets#version bump#npm publishing
One-click install
npx skills add https://github.com/yamcodes/the-hat --skill changeset-yamcodes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changeset
Source: https://github.com/yamcodes/the-hat/tree/main/skills/changeset
Command: npx skills add https://github.com/yamcodes/the-hat --skill changeset-yamcodes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It removes the guesswork from versioning by guiding the creation of changeset files with correct bump types, imperative-mood descriptions, and proper breaking-change documentation. ## Core Features & Use Cases - Bump Type Decision Guides: Distinguishes patch, minor, and major bumps under both v0 and v1+ SemVer rules, including prerelease (alpha/beta/rc) conventions. - Changeset Authoring & Editing: Enforces conventions such as #### headers, imperative mood, usage examples, and **BREAKING CHANGE**: notes when creating or modifying files in .changeset/. - Release Workflow Integration: Covers the full flow from pnpm changeset through the automated "Version Packages" PR and npm publication. - Use Case: After finishing a feature branch, ask the assistant to add a changeset; it selects the right bump type, writes a compliant description with a usage example, and validates it against the checklist before the PR. ## Quick Start Ask the assistant to create a changeset for the changes in your current branch using the changeset skill.

Frequently Asked Questions about changeset

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

FAQPage Schema
How do I create a changeset for a monorepo release?▼

Run pnpm changeset for an interactive prompt, or manually create a markdown file in .changeset/ with a random name. The file lists affected packages with bump types in frontmatter, followed by a #### imperative-mood title and description.

What bump type should I use for a breaking change in changesets?▼

In v1+ packages, breaking changes require a major bump with a **BREAKING CHANGE**: note at the bottom. In v0 packages, breaking changes use a minor bump, while major is reserved for the explicit transition to v1.0.0.

Should internal refactorings get a changeset entry?▼

No. Purely internal refactorings like library switches or type cleanups with no consumer-facing benefit should not be documented. Only changes meaningful to end users belong in the changelog.

Why is my changeset description considered invalid?▼

Descriptions must start with a #### header and use imperative mood ("Add helper", not "Adds" or "Added"). Past or indicative tense, GitHub issue references, and missing usage examples for user-facing changes are all style violations.

How do changesets trigger package publishing to npm?▼

Merging a PR with a changeset to the dev branch triggers the Changesets GitHub Action, which opens a Version Packages PR. Merging that PR publishes bumped packages to npm and fast-forwards main to dev.

Related Skills

Explore More Software Engineering Skills→
kang8kang8
2

commit

Create git commits from staged changes with branch naming and validation.

Community
Advanced
mia-cxmia-cx

setup-changesets

Configure and run changesets to publish versioned packages and changelogs.

Official
Intermediate
kubb-labskubb-labs
1.8k

pr

Enforces PR checklists, changeset creation, and release rules for monorepo contributions.

Official
Basic
reaatechreaatech
2

Changelog Generation

Generate CHANGELOG.md entries and version bumps from conventional commits using Changesets.

Community
Advanced