changeset

Create, propose, and apply Changesets for repository code changes.

63|2|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/stolinski/s-stack --skill changeset-stolinski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changeset
Source: https://github.com/stolinski/s-stack/tree/main/skills/changeset
Command: npx skills add https://github.com/stolinski/s-stack --skill changeset-stolinski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams automatically create, propose, and apply Changesets for code changes, aligning version bumps with changes in the codebase.

Core Features & Use Cases

  • Detect changes in the working tree and map them to affected packages in mono-repos or single-package repos.
  • Propose appropriate semver bumps (patch, minor, major) with rationale.
  • Create and apply changeset files in .changeset/ and apply pending changesets when requested.

Quick Start

Run the skill to generate a changeset for the current session.

Frequently Asked Questions about changeset

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

FAQPage Schema
How do I automate release notes and version bumps for a monorepo?

Changesets map changed files to affected packages and propose semver bump levels with rationale. This skill creates changeset files in the .changeset/ directory and applies pending version bumps when you confirm the changes.

How do I generate a changeset for my current code changes?

Run the skill against your working tree to detect code changes, map them to packages, and propose semver bumps. You then confirm the proposed patch, minor, or major version changes to create and apply the changeset files.

Do I need @changesets/cli installed to use this automation?

Yes, this skill requires @changesets/cli or equivalent tooling and an existing .changeset/ directory. These dependencies enable the skill to map changed files to packages and apply version bumps with user confirmation.

Can I use changesets for single-package repositories or only monorepos?

Changesets work with both monorepos and single-package repositories. The skill maps changed files to packages in either context, proposing appropriate semver bumps and generating changeset files for release notes.

What is the best way to manage semver versioning across multiple packages?

Using changesets to track modified files, map them to affected packages, and propose coordinated patch, minor, or major bumps with generated release notes is an effective approach for managing semver versioning across multiple packages.