changeset
/changeset
Use this skill when a Biome change may affect users and you must decide whether it needs a changeset, choose the release level, or create and edit `.changeset/*.md` release-note text. Do not use for implementation details or PR descriptions.
- Author
- modem-dev ↗
- Repository
- ossrules ↗
- Licence
- MIT
- Last repository change
- 21.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 21.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use this skill when a Biome change may affect users and you must decide whether it needs a changeset, choose the release level, or create and edit `.changeset/*.md` release-note text. Do not use for implementation details or PR descriptions.
Original author description
Use this skill when a Biome change may affect users and you must decide whether it needs a changeset, choose the release level, or create and edit `.changeset/*.md` release-note text. Do not use for implementation details or PR descriptions.
How it works
- Decide Whether One Is Required
- Choose the Release Level
- Create the File
- Write the Entry
- Review Checklist
- References
SKILL.md preview
--- name: changeset description: Use this skill when a Biome change may affect users and you must decide whether it needs a changeset, choose the release level, or create and edit `.changeset/*.md` release-note text. Do not use for implementation details or PR descriptions. compatibility: Designed for coding agents working on the Biome codebase (github.com/biomejs/biome). --- # Changesets Changesets describe user-visible behavior for release notes. Root `AGENTS.md` defines when automated contributions require one; `CONTRIBUTING.md` is canonical for package selection, versioning, branch targets, and prose format. ## Decide Whether One Is Required A changeset is required for behavior visible to users of the CLI, libraries, published crates, diagnostics, parser, formatter, linter, or assists. No changeset is needed for an internal refactor with identical behavior, tests only, CI/build maintenance, or documentation-only edits. Before opening a PR, explicitly confirm the user-facing classification as required by `AGENTS.md`. Do not infer user visibility only from the files changed. ## Choose the Release Level | Change | Level | Target | | --- | --- | --- | | Bug fix or non-breaking behavior correction | `patch` | `main` | | New nursery lint rule | `patch` | `main` | | New user-facing feature or nursery promotion | `minor` | `next` | | Breaking user API change | `major` | `next` | Nursery rules are the exception to the usual new-feature mapping because they do not follow semantic versioning. Verify unusual cases against the current versioning policy. ## Create the File Run `just new-changeset-empty` to generate an empty file. ```shell just new-changeset-empty ``` An empty generated entry starts with frontmatter delimiters. Replace that frontmatter with the package and release level rather than appending a second block: ```markdown --- "@biomejs/biome": patch --- Description. ``` Use `####` or `#####` for headings inside a longer entry. Other heading levels interfere with changelog generation. ## Write the Entry - Describe user-visible behavior, not implementation. - Use one to three sentences unless the impact genuinely needs an example. - Use past tense for the contribution and present tense for resulting Biome behavior. - Start bug fixes with the linked issue when one exists. - Link rule and assist names to their Biome website pages. - End every sentence with a full stop. Include only the example needed to understand impact: - new rule: an invalid example; - existing rule: what became valid or invalid; - formatter: a `diff` block; - parser: source that now parses or is now rejected. Do not copy a PR summary into the changeset. A changeset is release-note text and should omit test plans, internal design, and reviewer guidance. ## Review Checklist - The behavior is user-visible. - The package is correct. - The release level agrees with branch policy. - The description matches the implemented behavior. - Issue, rule, and assist links are accurate. - Examples show observable impact. - The file has one valid frontmatter block. ## References - Changeset policy: `CONTRIBUTING.md#changelog` - Branch targeting: `CONTRIBUTING.md#creating-pull-requests` - Versioning: https://biomejs.dev/internals/versioning/ - Generator recipes: `justfile`
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · modem-dev/ossrules | 100 | MIT |
| withastro/astro | 100 | MIT |
| sl-design-system/components | 100 | Apache-2.0 |
| yamcodes/arkenv | 100 | MIT |
| ShepardVasNormandy/claude-skills | 100 | MIT |
| tuanductran/hr-skills | 100 | MIT |
| stormix/transcripts-mcp | 100 | MIT |
| udecode/kitcn | 96 | Apache-2.0 |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version d946ec679a27 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100changeset-pr
Create or update a `.changeset/*.md` file for the current branch or PR in this repository, choose the correct package scope and release type, and verify the result against repo-specific Changesets config. Use when a publishable package changed, when a PR is missing a changeset,… - 100add-changeset
Write a changeset for agentic-seo-check as a file, without the interactive prompt, in the changelog's voice. Use when a change users notice needs one, or when asked to add a changeset or a changelog entry. - 100changeset-generator
Generates changeset files based on changes. Use when user asks to create a changeset or at the end of a feature implementation, when the user asks to wrap up or finalize changes - 100changesets
Create or refresh a `.changeset/<slug>.md` for the current branch, or report that none is required. Triggers on "/changesets create", "add a changeset", "create a changeset", "update the changeset", "refresh the changeset", "do I need a changeset", or any work that touches… - 100pr-changeset
Create changesets for package changes in pull requests. Invoke whenever any file under packages/* is modified — including bug fixes, new features, and even documentation or typo changes. Changesets are required before committing; without one, the release pipeline won't know what… - 100changesets
Write the changeset for a change in a repo that releases with changesets (a `.changeset/` folder exists). The bump level follows one question, whether the thing existed before: patch for changed behavior, minor for something new, major only with the maintainer's approval. Use…