biome-code-review

Reviews Biome pull requests and diffs through read-only static analysis with severity-ranked findings.

25.7k|1.2k|Updated Jul 27, 2023
One-click install
npx skills add https://github.com/biomejs/biome --skill biome-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: biome-code-review
Source: https://github.com/biomejs/biome/tree/main/.claude/skills/biome-code-review
Command: npx skills add https://github.com/biomejs/biome --skill biome-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reviewing changes to the Biome toolchain requires deep knowledge of its crates, workspace execution model, and contribution process, and mistakes like unsafe fixes, missing registrations, or workspace races are easy to miss in manual review.

Core Features & Use Cases

  • Scoped Static Review: Reviews a PR, branch, commit range, diff, or working tree against the correct merge base without editing files or running project code.
  • Subsystem-Aware Checks: Routes diffs to targeted references covering lint rules, parsers, formatters, diagnostics, type inference, Rust safety, and workspace access.
  • Structured Findings Report: Returns severity-tagged findings (high/medium/low/optional) with file locations, triggers, impact, and remediation direction, plus changeset and branch-target status.
  • Use Case: A maintainer asks for a review of PR #1234 in biomejs/biome; the skill reads the diff, inspects affected callers and tests, and reports a high-severity incorrect safe fix with a minimal remediation direction.

Quick Start

Review the changes in PR 1234 of the biome repository and report any correctness, safety, or process findings.

Frequently Asked Questions about biome-code-review

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

FAQPage Schema
How do I review a Biome pull request with this skill?

Provide the PR number and the skill reads its title, body, base, and diff using gh pr view and gh pr diff without checking it out. It then inspects every changed file, affected callers, and tests, returning severity-ranked findings in a structured Markdown report.

What kinds of issues does Biome code review detect?

It detects regressions, incorrect safe fixes, user-reachable panics, unjustified partial operations like unwrap and indexing, workspace execution races, missing registrations, and changeset or branch-target process violations. Findings are tagged by severity and area with remediation direction.

Does the review run tests or modify the working tree?

No. The review is strictly read-only static analysis: it never edits files, runs builds, tests, formatters, or linters, and limits shell use to a fixed set of git and gh read commands plus one allowed base-branch fetch.

When should I not use this code review skill?

Do not use it for triage, reproduction, or implementation tasks, and it only fits the Biome codebase at github.com/biomejs/biome. It also cannot verify runtime behavior since no project code is executed during review.

Can the review handle uncommitted or untracked changes?

Yes. When no PR is given, it diffs the merge base through the working tree so committed, staged, and unstaged changes are included, and it reads every untracked file such as new tests and changesets.