changesets

Writes changeset files with correct bump levels for repository releases.

2|1|Updated Jun 28, 2026
One-click install
npx skills add https://github.com/lxsmnsyc/overwander --skill changesets-lxsmnsyc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changesets
Source: https://github.com/lxsmnsyc/overwander/tree/main/.agents/skills/changesets
Command: npx skills add https://github.com/lxsmnsyc/overwander --skill changesets-lxsmnsyc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Every change to this repository must ship with a changeset, and choosing the wrong bump level or writing changelog prose aimed at the wrong audience produces misleading release notes. This Skill encodes the repository's rules so every task ends with a correct changeset without being asked. ## Core Features & Use Cases - Bump level selection: Decides between patch (existing behavior changed), minor (something new exists), and major (only with maintainer approval), taking the higher level when a change does both. - Changeset authoring: Creates kebab-case markdown files in .changeset/ with the overwander package name, short prose, no em-dashes, and 80-column wrapping. - Duplicate prevention: Checks CHANGELOG.md before writing, since the release step folds changesets in and empties the directory. - Use Case: After fixing a rendering bug and adding a new weather type on one branch, the Skill writes one changeset at minor level describing both changes as a short list. ## Quick Start Write a changeset for the change just made on this branch, choosing the correct bump level and following the repository prose rules.

Frequently Asked Questions about changesets

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

FAQPage Schema
How do I choose between patch and minor in a changeset?▼

Ask whether the thing existed before. If something that already existed now behaves differently, it is patch; if something exists now that did not before, it is minor. When one change does both, take the higher level.

How do I write a changeset for the changesets tool?▼

Create a kebab-case markdown file in .changeset/ with frontmatter mapping the package name to the bump level, followed by one short line describing what is true now. Use a list when the change covers several things.

When should a changeset use a major bump?▼

Never on your own judgement. A major bump requires the maintainer's explicit approval, so state what you think warrants it and let the maintainer decide.

Does a fix for a bug introduced on the same branch need a changeset?▼

No. Changesets describe what changed against main, so a correction to something that never reached main gets no changeset of its own. Amend the feature's own changeset if it now claims something untrue.

Why is the .changeset directory empty after a release?▼

The release step folds every changeset into CHANGELOG.md and empties .changeset/. Check CHANGELOG.md before writing a second changeset for something already shipped.