菜单
Guide for creating proper pull requests for the Biome project. Use when opening a PR, writing a PR description, choosing the correct target branch, or filling out the PR template. Trigger when creating PRs, writing PR summaries, or preparing code for review.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/biomejs/biome --skill pull-request命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Static, read-only code review of a Biome (github.com/biomejs/biome) pull request, local branch, commit range, diff, or working tree being prepared as a PR. Applies Biome's own conventions - nursery placement and naming for lint rules, diagnostics quality, allocation and borrow discipline around TokenText and SyntaxToken, parser error recovery, formatter IR and idempotency, codegen freshness, insta snapshots, dev-dependency paths, doc style, changesets, branch targeting, PR titles, and AI disclosure. Only when asked to review a Biome pull request, branch, commit range, diff, or working tree. Not for issue triage, bug reproduction, or implementing fixes. Reports findings only - never edits files or runs cargo, just, pnpm, tests, builds, or codegen.
How to write inline comments, rustdoc, and module documentation in the Biome codebase. The audience is Biome developers reading the source, not end users. Use whenever writing or editing `//` comments, `///` item docs, or `//!` module docs — including comments added incidentally while fixing bugs or implementing features.
General development best practices and common gotchas when working on Biome. Use for avoiding common mistakes, understanding Biome-specific patterns (AST, syntax nodes, string extraction, embedded languages), and learning technical tips.
正在显示 SKILL.md
基于 SOC 职业分类
| name | pull-request |
| description | Guide for creating proper pull requests for the Biome project. Use when opening a PR, writing a PR description, choosing the correct target branch, or filling out the PR template. Trigger when creating PRs, writing PR summaries, or preparing code for review. |
| compatibility | Designed for coding agents working on the Biome codebase (github.com/biomejs/biome). |
Use this skill when creating a pull request for the Biome repository. It covers branch targeting, title formatting, the PR template, and AI disclosure requirements.
If AI was used in any capacity to produce the PR, you must disclose it in the PR description. Examples:
This PR was written primarily by Claude Code.
I consulted ChatGPT to understand the codebase but the solution was fully authored manually by myself.
This is mandatory. It helps reviewers apply appropriate scrutiny.
| Change type | Target branch |
|---|---|
| Bug fix (code or docs) | main |
| New nursery rule | main |
| Rule promotion from nursery | next |
| New feature (user-facing) | next |
| New feature (internal only) | main |
Use conventional commit format. The title becomes the squash-merge commit message.
<type>(<scope>): <short description>
Supported prefixes:
feat: — new featurefix: — bugfixdocs: — documentation updaterefactor: — code refactor (no behavior change)test: — test updatechore: — housekeepingperf: — performance improvementci: — CI changebuild: — build system or dependency changerevert: — revert a previous changeExamples:
feat(css): add noDuplicateSelectors rule
fix(linter): handle edge case in useOptionalChain
docs: update contributing guide
refactor(parser): simplify HTML attribute parsing
The CI runs action-semantic-pull-request to validate the title. Fix it if the workflow fails.
The repository has a PR template at .github/PULL_REQUEST_TEMPLATE.md. Every PR description must follow this structure:
## Summary
<!-- Explain the motivation for this change. What problem does it solve? -->
<!-- Link relevant issues or Discord discussions. -->
<!-- If user-facing, mention the changeset. -->
## Test Plan
<!-- What demonstrates correctness? Mention tests added/updated. -->
## Docs
<!-- For new rules/actions/options: docs are inline in the code (rustdoc). -->
<!-- For other features: link a docs PR to the `next` branch of biomejs/website. -->
Fixes #1234 or Related to #5678.Keep it brief. Examples:
Do not list individual test files — the diff speaks for itself. If automated tests were not possible, state that manual testing is required.
next branch of biomejs/website.N/A under the section.Before opening, ensure:
cargo checkcargo test (or just test-crate <crate> for scoped runs)just fjust ljust gen-rules && just gen-configurationjust gen-grammar <lang>just gen-bindingsjust new-changeset-emptycargo insta reviewCONTRIBUTING.md sections "Commit messages" and "Creating pull requests".github/PULL_REQUEST_TEMPLATE.md