changeset
This skill walks you through building changesets for Biome pull requests that introduce user-facing changes—bug fixes, new features, rule updates, or formatter tweaks. It covers selecting the right change type (patch, minor, or major), formatting rules, and writing clear descriptions with examples. Use it whenever your PR needs a CHANGELOG entry.
changeset guides you through creating and formatting changeset entries for Biome pull requests with user-visible changes.
AI-generated summary based on this skill's SKILL.md
Install
biomejs/biome/changeset · repository language: Rust
git clone https://github.com/biomejs/biome
cp -r biome/.claude/skills/changeset ~/.claude/skills/changesetnpx skillfed install biomejs/biome/changesetFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I create a changeset for Biome?
changeset guides you through building changesets for Biome pull requests. To create one, run `pnpm biome just new-changeset-empty` in the repo root. This generates a new file in the `.changeset/` directory with a template you fill in with your change type (patch, minor, or major), affected package, and a clear description of what changed and why.
What is the correct changeset format for a Biome PR?
changeset requires a YAML-like structure in `.changeset/` files. Include the package name, change type (patch/minor/major), and a markdown description. Use past tense ("Fixed bug" not "Fix bug"), keep descriptions concise, and reference the specific rule, formatter behavior, or parser change affected. Markdown formatting like headers and code blocks is supported.
How do I determine patch, minor, or major for a changeset?
changeset uses semantic versioning: patch for bug fixes and small improvements, minor for new features and rule additions, major for breaking changes. A new lint rule is typically minor; a formatter behavior change or parser fix is usually patch; removing a rule or changing its default is major. Choose based on user impact.
When do I need a changeset in a Biome PR?
changeset is required for any PR introducing user-facing changes—new rules, bug fixes, formatter tweaks, or parser updates. Refactoring, documentation, or internal improvements typically do not need a changeset. If unsure, check the PR guidelines; the CI will flag missing changesets for changes that warrant a CHANGELOG entry.
Can you show a changeset example for a bug fix?
changeset for a bug fix might look like: package name `@biomejs/biome`, type `patch`, description "Fixed incorrect indentation in JSX attribute lists." Use past tense, be specific about what broke and how it's now corrected. For a new rule, use type `minor` and describe the rule's purpose and default behavior.
What are changeset best practices for formatter and rule changes?
changeset best practices: write descriptions in past tense, mention the specific rule or formatter component affected, explain the user-visible change clearly, and keep it concise. For rule changes, note if it's a new rule, a behavior update, or a default toggle. For formatter changes, describe the formatting behavior shift and affected syntax.
SKILL.md
rendered from the published skill — quoted content, verbatim
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
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.claude/skills/changeset/SKILL.md