How do I install the Changeset skill?

Run npx skillmds@latest add tomevault-io/changeset in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Changeset safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: WARNING. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Changeset?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Changeset free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Changeset?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Changeset by tomevault-io — Agent Skill

Name: Changeset
Author: tomevault-io

File contents

Changeset Creation Skill

Create changeset files for projects using @changesets/cli.

Context

Existing changesets: !ls .changeset/*.md 2>/dev/null | head -5
Workspace packages: !find packages plugins -maxdepth 2 -name package.json -exec jq -r .name {} \; 2>/dev/null | sort

Instructions

Step 1: Detect Packages

This is a monorepo with workspaces in packages/* and plugins/*
Find all package.json files in workspace directories and extract names
IMPORTANT: Never use the root package name ("root") - only use actual workspace package names
Common packages for app-wide changes: app, backend

Step 2: Gather Information

Use AskUserQuestion tool to ask:

Package Selection (if multiple packages): Which packages should be included? Use multiSelect: true to allow selecting multiple packages.
Version Bump Type: For each selected package - patch, minor, or major?
Summary: Brief description of changes for the changelog

Step 3: Generate Unique Filename

Generate a unique file name for the changeset by running the script .claude/skills/changeset/generate-file-name.sh.

Step 4: Write Changeset File

Create the file with the name obtained in step 3 with the following content:

---
'package-name': patch
---

Summary description here.

Rules:

Package names MUST be quoted
Only use actual workspace package names (e.g., app, backend, @giantswarm/backstage-plugin-gs)
NEVER use the root package name ("root") - it will break yarn changeset version
End file with newline
Create .changeset/ directory if missing

Step 5: Confirm

Display:

Path to created changeset
File contents
Remind user to commit the file

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: changesetdescription: Create a changeset file for versioning packages. Use when the user wants to document changes for release, create a changelog entry, or bump package versions. Use when this capability is needed.---# Changeset Creation SkillCreate changeset files for projects using @changesets/cli.## Context- Existing changesets: !`ls .changeset/*.md 2>/dev/null | head -5`- Workspace packages: !`find packages plugins -maxdepth 2 -name package.json -exec jq -r .name {} \; 2>/dev/null | sort`## Instructions### Step 1: Detect Packages1. This is a monorepo with workspaces in `packages/*` and `plugins/*`2. Find all `package.json` files in workspace directories and extract names3. **IMPORTANT**: Never use the root package name ("root") - only use actual workspace package names4. Common packages for app-wide changes: `app`, `backend`### Step 2: Gather InformationUse AskUserQuestion tool to ask:1. **Package Selection** (if multiple packages): Which packages should be included? Use multiSelect: true to allow selecting multiple packages.2. **Version Bump Type**: For each selected package - patch, minor, or major?3. **Summary**: Brief description of changes for the changelog### Step 3: Generate Unique FilenameGenerate a unique file name for the changeset by running the script `.claude/skills/changeset/generate-file-name.sh`.### Step 4: Write Changeset FileCreate the file with the name obtained in step 3 with the following content:```markdown---'package-name': patch---Summary description here.```Rules:- Package names MUST be quoted- Only use actual workspace package names (e.g., `app`, `backend`, `@giantswarm/backstage-plugin-gs`)- NEVER use the root package name ("root") - it will break `yarn changeset version`- End file with newline- Create `.changeset/` directory if missing### Step 5: ConfirmDisplay:1. Path to created changeset2. File contents3. Remind user to commit the file---> Converted and distributed by [TomeVault](https://tomevault.io/claim/giantswarm) — claim your Tome and manage your conversions.

Frequently asked questions

Changeset