skills.rest
matsumuratk
matsumuratkCOMMUNITY
Explore all skills by this author →
GitHub

add-changeset

Create changeset markdown files documenting user-facing changes for release notes.

1|Updated Jul 12, 2026
Search Tags:#changelog#versioning#markdown#release notes#monorepo#create#changeset
One-click install
npx skills add https://github.com/matsumuratk/elmo-aws --skill add-changeset-matsumuratk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-changeset
Source: https://github.com/matsumuratk/elmo-aws/tree/main/elmo/.claude/skills/add-changeset
Command: npx skills add https://github.com/matsumuratk/elmo-aws --skill add-changeset-matsumuratk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-formatted changeset entries for release notes is repetitive and easy to get wrong. This Skill generates properly formatted changeset files in the .changeset/ directory so your releases always have accurate, user-facing documentation. ## Core Features & Use Cases - Changeset File Generation: Creates a markdown file in .changeset/ with the correct YAML frontmatter listing affected packages and bump types. - Writing Guidance: Enforces concise, past-tense descriptions focused on user impact rather than implementation details. - Use Case: After implementing a bug fix in a monorepo, ask the assistant to add a changeset; it produces a file like fix-login-redirect.md with the affected packages marked as patch and a one-sentence description. ## Quick Start Add a changeset for the login redirect fix that patches the @elmohq/cli package.

Frequently Asked Questions about add-changeset

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

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

Create a markdown file in the .changeset directory with YAML frontmatter listing affected packages and their bump type, followed by a one-sentence description. This Skill generates that file automatically with the correct format.

When should I add a changeset to a pull request?▼

Add a changeset for any user-facing change such as new features, bug fixes, or behavior changes. Skip changesets for pure refactors and docs-only changes that do not affect users.

What bump type should a changeset use by default?▼

Default to patch unless the user explicitly requests a different bump. List only the packages actually affected by the change in the frontmatter.

How long should a changeset description be?▼

Keep it to one concise sentence of roughly 160 characters or fewer. Use past tense for what the PR did, plain text without formatting, and end with a full stop.

Can one pull request have multiple changesets?▼

Yes, but it is rare. Most PRs need a single changeset; multiple changesets are only occasionally appropriate when a PR contains distinct user-facing changes.

Related Skills

Explore More Software Engineering Skills→
reactivereactive
2.0k

changeset

Generate user-focused changesets, changelog entries, and release documentation for semver package bumps.

Official
Intermediate
pohlai88pohlai88

changesets

Automate multi-package versioning and changelog management in monorepos.

Community
Advanced
DataDogDataDog
417

write-changelog

Write customer-facing changelog fragments for Ruby gem pull requests.

Official
Intermediate
devantler-techdevantler-tech
2

conventional-release

Write Conventional Commit PR titles and commit messages for automated releases.

Official
Intermediate