changeset

name	changeset
description	Guide for creating and writing proper changesets for Biome PRs. Use when a PR introduces user-visible changes (bug fixes, new features, rule changes, formatter changes, parser changes) that need a changeset entry for the CHANGELOG. Trigger when creating changesets, writing changeset descriptions, or choosing the correct change type.
compatibility	Designed for coding agents working on the Biome codebase (github.com/biomejs/biome).

Purpose

Use this skill when a PR introduces user-facing changes that require a changeset. Changesets drive CHANGELOG generation and release automation. Internal-only changes (refactors with no user-visible effect) do not need changesets.

Create a Changeset

Do not create changeset files manually. Use:

just new-changeset-empty

The command will create a file in .changeset/. Edit it directly to add detail.

Note that the file will not be literally empty. It will have this content:

---
---

Do not simply append to the changeset description below the existing content, which creates an invalid changeset.

Requires pnpm — run pnpm i from repo root first.

Choose the Correct Change Type

• patch — Bug fixes.
• minor — New features. PR must target the next branch.
• major — Breaking user API changes. PR must target the branch. These are rare and strictly controlled.