changeset

Create standardized changesets for Biome PRs to document user-facing changes.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/qdhenry/Foundry-OSS --skill changeset-qdhenry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changeset
Source: https://github.com/qdhenry/Foundry-OSS/tree/main/.agents/skills/changeset
Command: npx skills add https://github.com/qdhenry/Foundry-OSS --skill changeset-qdhenry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changesets drive CHANGELOG generation and release automation. They are required when PRs introduce user-visible changes; internal-only changes do not require a changeset.

Core Features & Use Cases

  • Create a changeset using the recommended workflow to document user-visible changes.
  • Choose the correct change type (patch, minor, major) to reflect impact on releases.
  • Format changesets consistently so release tooling can generate changelogs automatically.
  • Use within Biome projects to trigger changelog updates and release automation.

Quick Start

Run just new-changeset-empty to create an empty changeset file, then edit it to add detail.

Frequently Asked Questions about changeset

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a changeset for a Biome PR?

A changeset for a Biome PR is created by running the 'just new-changeset-empty' command to generate an empty file, which you then edit to document your user-visible changes.

When do I need to add a changeset to my pull request?

You need to add a changeset to your pull request when the code changes introduce user-visible modifications; internal-only changes that do not impact users do not require a changeset.

How do I choose the correct change type for a changeset?

You choose the correct changeset change type by selecting patch, minor, or major based on the impact your modifications have on releases, ensuring release tooling can generate changelogs automatically.

Does Biome release automation require a specific changeset format?

Yes, Biome release automation requires a standardized changeset format to correctly drive CHANGELOG generation and trigger automated releases without manual formatting errors.

What happens if I skip changesets for internal-only codebase changes?

Skipping changesets for internal-only codebase changes is expected because changesets are only required to document user-facing changes that need to appear in the generated CHANGELOG.