pull-request
This skill walks you through the pull request workflow for the Biome project, covering branch selection based on change type, conventional commit title formatting, and the required PR template structure. It ensures you disclose any AI assistance used and prepare your code for review with the right context and test documentation.
pull-request guides you through creating properly formatted pull requests for the Biome repository, including branch selection and template compliance.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-27
pull-request guides you through creating properly formatted pull requests for the Biome repository, including branch selection and template compliance. This skill walks you through the pull request workflow for the Biome project, covering branch selection based on change type, conventional commit title formatting, and the required PR template structure. It ensures you disclose any AI assistance used and prepare your code for review with the right context and test documentation.
Use it when
- The pull-request skill covers Biome's PR template, which includes sections for describing your changes, explaining the motivation.
- The pull-request skill teaches branch targeting based on change type.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
biomejs/biome/pull-request · repository language: Rust
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I create a pull request for Biome?
The pull-request skill guides you through Biome's complete PR workflow. Start by selecting the correct target branch based on your change type, then format your title using conventional commit syntax (e.g., `fix:`, `feat:`, `docs:`). Fill out the required PR template with a clear description, test plan, and documentation updates. Disclose any AI assistance used in development, and ensure your code is ready for peer review before submitting.
What is the Biome PR template structure and required sections?
The pull-request skill covers Biome's PR template, which includes sections for describing your changes, explaining the motivation, documenting your test plan, and noting any documentation updates needed. The template ensures consistency across contributions and helps reviewers understand the scope and impact of your work. Following the template structure is essential for validation and smooth review.
How do I choose the correct target branch for my Biome change?
The pull-request skill teaches branch targeting based on change type. Different modifications—bug fixes, features, or documentation—may target different branches in the Biome repository. Understanding which branch to select ensures your PR reaches the right maintainers and follows the project's release workflow, preventing validation failures and delays.
What is the conventional commit format for Biome PR titles?
The pull-request skill explains that Biome uses conventional commit formatting for PR titles. This format includes a type prefix (`fix`, `feat`, `docs`, `refactor`, etc.) followed by a colon and a concise description. Proper formatting enables automated changelog generation and helps maintainers quickly categorize contributions. The semantic pull request action validates compliance with this standard.
How should I disclose AI usage in a Biome pull request?
The pull-request skill emphasizes transparency in your PR submission. If you used AI assistance during development, disclose it clearly in your PR description or comments. This transparency helps reviewers understand the code's origin and context, ensuring ethical contribution practices and maintaining trust within the Biome community.
What should I include in my Biome PR test plan and documentation?
The pull-request skill guides you to document your testing approach and any documentation changes. Your test plan should explain how reviewers can verify your changes work correctly. Include updates to relevant docs sections if your change affects user-facing behavior or APIs. This preparation demonstrates thoroughness and accelerates the review process.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Purpose
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.
AI Assistance Disclosure
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.
Choose the Target Branch
| 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) |
(truncated - see the full file via the links below)
File tree — 1 file
.claude/skills/pull-request/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Create a properly formatted pull request for the Biome project”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
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.
testing-codegen guides you through snapshot testing with insta and code generation for the Biome codebase. It covers running tests for specific crates, fast iteration with quick-test workflows, and safely managing snapshots—including pruning orphaned files and reviewing changes interactively. Use this skill when testing lint rules, inspecting AST structure, or regenerating parser and analyzer code.
This skill establishes documentation standards for Biome developers writing comments and rustdoc in the codebase. It distinguishes three comment types—module docs for explanation, item docs for reference, and inline comments for rationale—and teaches which patterns to avoid. The core principle: write for future contributors with no access to your current context, stating how code works rather than how it came to be.
This skill guides you through building new lint rules and assist actions for Biome. It covers rule scaffolding across multiple languages, implementation patterns with semantic analysis, code action setup, and the three-pillar diagnostic framework required for all rules. Use it when adding custom rules like noVar or useConst to Biome's codebase.
This skill guides you through building option migrators for the `biome migrate eslint` command, preserving ESLint rule configurations beyond severity alone. Learn to model ESLint options in Rust, convert them to Biome equivalents, wire typed rule variants into the migration pipeline, and test through fixture-driven specs.
Learn to implement and modify Biome's formatters using its trait-based IR system. This skill covers generating formatter boilerplate, writing FormatNodeRule implementations, managing comments in formatted output, and validating your work against Prettier using snapshot tests and idempotency checks.
More skills biome-developer (Apache-2.0) · biome (MIT) · Npm Package (unlicensed) · parser-development (Apache-2.0)