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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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.
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.
| 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.
Run just new-changeset-empty to generate an empty file.
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:
---
"@biomejs/biome": patch
---
Description.
Use #### or ##### for headings inside a longer entry. Other heading levels interfere with changelog generation.
Include only the example needed to understand impact:
diff block;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.
CONTRIBUTING.md#changelogCONTRIBUTING.md#creating-pull-requestsjustfileNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a user says "add a ty diagnostic", "write this new ty diagnostic", "change a ty error message", "review ty diagnostics", or asks to add, update, or review ty checks, diagnostic messages, subdiagnostics, or concise output behavior.
The English summary is being prepared. Showing the original description.
Use when adding A2UI rendering to any AG-UI-supported framework or custom AG-UI application, scaffolding an AG-UI app that should render A2UI, adapting an AG-UI integration to emit A2UI surfaces, or wiring the AG-UI A2UI middleware/toolkit with a compatible renderer.
The English summary is being prepared. Showing the original description.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
The English summary is being prepared. Showing the original description.
Evaluate an open source project's AGENTS.md and produce a corpus entry for the /agents-md directory. Use when adding a project to the directory, refreshing an existing entry, or running a batch of candidate repositories.
The English summary is being prepared. Showing the original description.
Execute Anarlog work immediately while recording issues, decisions, progress, and lessons in Linear. Use for Anarlog repository or Anarlog desktop, web, mobile, and API work, including related worktrees and ANLG issues. Explicit brainstorming stays discussion-first. Do not use for unrelated repositories or meeting-data queries.
The English summary is being prepared. Showing the original description.
Use only for reviewing completed Biome PRs, branches, commit ranges, diffs, or working trees against business logic and requirements. Excludes broad code-quality and process audits, triage, reproduction, and implementation.
The English summary is being prepared. Showing the original description.