# Changeset

> 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.

- Skill: `tomevault-io/changeset` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/changeset`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/changeset/raw
- Safety review: PASS (external: skill-scanner WARNING, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/changeset

---


# 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

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

### Step 2: Gather Information

Use 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 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:

```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: Confirm

Display:

1. Path to created changeset
2. File contents
3. Remind user to commit the file

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/giantswarm) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->