How do I install the Changeset skill?

Run npx skillmds@latest add openzeppelin-contracts-wizard/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.

What does the Changeset skill do?

Add a changeset file for a package version bump It is listed under Coding & Dev Tools on SkillMD.

Is Changeset safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. 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?

OpenZeppelin (@openzeppelin-contracts-wizard) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Changeset by openzeppelin-contracts-wizard

Name: Changeset
Rating: 4.2 (5 reviews)
Author: OpenZeppelin

File contents

Add Changeset

Create a changeset file in .changeset/ for the specified package(s).

Format

---
'package-name': patch|minor|major
---

First line is a high-level summary without leading dash (PR number gets appended automatically).
- Additional detail line.
- Another detail line.
- **Breaking change**: Description of what breaks.

Rules

First line: Write as a plain sentence, no leading dash. The release tooling appends the PR link to this line.
Subsequent lines: Start each line with a dash. These lines get 2 spaces prepended automatically during the release process, so they appear indented under the first line in CHANGELOG.md.
Breaking changes: Mark with Breaking change or Breaking changes (see format example above).
File naming: Use a short kebab-case description, e.g., add-cli-package.md, move-schemas-to-common.md.
Multiple packages: Multiple packages can share a changeset file with different bump levels in the frontmatter. Use separate files only when packages need unrelated descriptions.
Bump levels: Follow semver based on current package version. x.y.z (>=1.0.0): major for breaking, minor for features, patch for fixes. 0.x.y: minor for breaking, patch for features/fixes. 0.0.x: patch for everything.
New unpublished packages: Still need a changeset to bump the initial version in package.json and for the changes to appear in the resulting changelog.
UI that ships in MCP Apps: ui is private (versioned in-repo, not published to npm). MCP App HTML is built from ui when @openzeppelin/contracts-mcp is published, but only from the packages/ui/src/mcp-apps/ bundle graph — the entries import the Wizard controls directly, not the web shells. Changes to modules reachable from src/mcp-apps/ need one changeset listing both ui and @openzeppelin/contracts-mcp; never version ui without also listing @openzeppelin/contracts-mcp. Web-only UI needs no changeset: the App.svelte shells and modules imported only by them (e.g. solidity/overrides.ts, solidity/remix.ts, common/post-config.ts), plus Cairo Alpha and Polkadot. To decide, search packages/ui/src/mcp-apps/ for imports of the changed modules. changeset status in CI still flags most packages/ui/src paths as needing a changeset, so a web-only UI PR gets the ignore-changeset label instead of a changeset.

Steps

Determine which packages changed and what bump level each needs.
Review existing CHANGELOG.md for the package(s) to match tone and style.
Write the changeset file(s) to .changeset/<descriptive-name>.md.

---name: changesetdescription: Add a changeset file for a package version bump---# Add ChangesetCreate a changeset file in `.changeset/` for the specified package(s).## Format```markdown---'package-name': patch|minor|major---First line is a high-level summary without leading dash (PR number gets appended automatically).- Additional detail line.- Another detail line.- **Breaking change**: Description of what breaks.```## Rules1. **First line**: Write as a plain sentence, no leading dash. The release tooling appends the PR link to this line.2. **Subsequent lines**: Start each line with a dash. These lines get 2 spaces prepended automatically during the release process, so they appear indented under the first line in CHANGELOG.md.3. **Breaking changes**: Mark with **Breaking change** or **Breaking changes** (see format example above).4. **File naming**: Use a short kebab-case description, e.g., `add-cli-package.md`, `move-schemas-to-common.md`.5. **Multiple packages**: Multiple packages can share a changeset file with different bump levels in the frontmatter. Use separate files only when packages need unrelated descriptions.6. **Bump levels**: Follow semver based on current package version. `x.y.z` (>=1.0.0): major for breaking, minor for features, patch for fixes. `0.x.y`: minor for breaking, patch for features/fixes. `0.0.x`: patch for everything.7. **New unpublished packages**: Still need a changeset to bump the initial version in package.json and for the changes to appear in the resulting changelog.8. **UI that ships in MCP Apps**: `ui` is private (versioned in-repo, not published to npm). MCP App HTML is built from `ui` when `@openzeppelin/contracts-mcp` is published, but only from the `packages/ui/src/mcp-apps/` bundle graph — the entries import the Wizard controls directly, not the web shells. Changes to modules reachable from `src/mcp-apps/` need **one changeset listing both** `ui` and `@openzeppelin/contracts-mcp`; never version `ui` without also listing `@openzeppelin/contracts-mcp`. Web-only UI needs **no changeset**: the `App.svelte` shells and modules imported only by them (e.g. `solidity/overrides.ts`, `solidity/remix.ts`, `common/post-config.ts`), plus Cairo Alpha and Polkadot. To decide, search `packages/ui/src/mcp-apps/` for imports of the changed modules. `changeset status` in CI still flags most `packages/ui/src` paths as needing a changeset, so a web-only UI PR gets the `ignore-changeset` label instead of a changeset.## Steps1. Determine which packages changed and what bump level each needs.2. Review existing CHANGELOG.md for the package(s) to match tone and style.3. Write the changeset file(s) to `.changeset/<descriptive-name>.md`.

Frequently asked questions

Changeset