Official agent skill

Promote Lint Rules

A skill your agent uses when promoting one or more Biome lint rules from nursery to stable groups, including promotion plans from GitHub issues, metadata changes, rule renames, generated…

OfficialApache-2.0Auto-check passedDevelopment

Install Promote Lint Rules

skills CLI

$ npx skills add biomejs/biome --skill promote-lint-rules -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install biomejs/biome promote-lint-rules --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/biomejs/biome.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/promote-lint-rules .claude/skills/promote-lint-rules && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "promote-lint-rules" agent skill from https://github.com/biomejs/biome/tree/main/.claude/skills/promote-lint-rules into .claude/skills/promote-lint-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "promote-lint-rules", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/biomejs/biome/tree/main/.claude/skills/promote-lint-rules

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add biomejs/biome --skill promote-lint-rules -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install biomejs/biome promote-lint-rules --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/biomejs/biome.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/promote-lint-rules .agents/skills/promote-lint-rules && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "promote-lint-rules" agent skill from https://github.com/biomejs/biome/tree/main/.claude/skills/promote-lint-rules into .agents/skills/promote-lint-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "promote-lint-rules", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add biomejs/biome --skill promote-lint-rules -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install biomejs/biome promote-lint-rules --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/biomejs/biome.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/promote-lint-rules .cursor/skills/promote-lint-rules && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "promote-lint-rules" agent skill from https://github.com/biomejs/biome/tree/main/.claude/skills/promote-lint-rules into .cursor/skills/promote-lint-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "promote-lint-rules", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/biomejs/biome.git --path .claude/skills/promote-lint-rules

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add biomejs/biome --skill promote-lint-rules -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install biomejs/biome promote-lint-rules --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/biomejs/biome.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/promote-lint-rules .gemini/skills/promote-lint-rules && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "promote-lint-rules" agent skill from https://github.com/biomejs/biome/tree/main/.claude/skills/promote-lint-rules into .gemini/skills/promote-lint-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "promote-lint-rules", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install biomejs/biome promote-lint-rules

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add biomejs/biome --skill promote-lint-rules -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/biomejs/biome.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/promote-lint-rules .github/skills/promote-lint-rules && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "promote-lint-rules" agent skill from https://github.com/biomejs/biome/tree/main/.claude/skills/promote-lint-rules into .github/skills/promote-lint-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "promote-lint-rules", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add biomejs/biome --skill promote-lint-rules -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install biomejs/biome promote-lint-rules --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/biomejs/biome.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/promote-lint-rules .opencode/skills/promote-lint-rules && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "promote-lint-rules" agent skill from https://github.com/biomejs/biome/tree/main/.claude/skills/promote-lint-rules into .opencode/skills/promote-lint-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "promote-lint-rules", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: promote-lint-rules
GitHub stars: 26k
Token cost: ~948 tokens
SKILL.md length: 418 words
Files: 1
Skills in repo: 12
Repo updated: Oct 10, 2026
First seen: Oct 8, 2026
Licence: Apache-2.0

At a glance

A skill your agent uses when promoting one or more Biome lint rules from nursery to stable groups, including promotion plans from GitHub issues, metadata changes, rule renames, generated…

Works in 4 steps: Read the complete requirements. For a… → Verify every listed current rule exists… → Resolve incomplete or malformed… → …
More Biome lint rules from nursery to stable groups
SKILL.md covers Build the Manifest, Apply the Plan, Generate and Test and Release Entry and Cleanup
Calls just and git

What it does

Promote Lint Rules is an agent skill from biomejs/biome, published by the product's own GitHub organization. Use this skill when promoting one or more Biome lint rules from nursery to stable groups, including promotion plans from GitHub issues, metadata changes, rule renames, generated configuration, and promotion snapshots.

Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Designed for coding agents working on the Biome codebase (github.com/biomejs/biome).

It sits in Development, covering Linting and formatting. It works with GitHub and JavaScript. The repository describes itself as: A toolchain for web projects, aimed to provide functionalities to maintain them. Biome offers formatter and linter, usable via CLI and LSP. The licence is Apache-2.0.

When your agent uses it

More Biome lint rules from nursery to stable groups
Including promotion plans from GitHub issues
Metadata changes
Generated configuration

Example prompts

“/promote-lint-rules”

Requirements

Compatibility (from SKILL.md): Designed for coding agents working on the Biome codebase (github.com/biomejs/biome).

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Read the complete requirements. For a GitHub issue, read both its body and comments.
Verify every listed current rule exists under a crates/biome_*_analyze/src/lint/nursery/ directory.
Resolve incomplete or malformed requirements before editing. Do not infer missing group, recommendation, severity, or rename decisions…
Create a temporary JSON file outside the repository, such as /tmp/biome-rule-promotions.json.

What it can do on your machine

Read from SKILL.md and the folder at commit fd4df34. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- just
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for coding agents working on the Biome codebase (github.com/biomejs/biome).
From compatibility in the SKILL.md frontmatter.

Context cost

Promote Lint Rules loads about 948 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 418 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~59
When it runs · the whole SKILL.md, loaded when a task matches: ~948

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from biomejs/biome at commit fd4df34, republished under its Apache-2.0 licence (© biomejs). 418 words, ~948 tokens.

Download SKILL.mdSave it as .claude/skills/promote-lint-rules/SKILL.md (or your agent's skills folder).

name: promote-lint-rules
description: Use this skill when promoting one or more Biome lint rules from nursery to stable groups, including promotion plans from GitHub issues, metadata changes, rule renames, generated configuration, and promotion snapshots.
compatibility: Designed for coding agents working on the Biome codebase (github.com/biomejs/biome).
disable-model-invocation: true

Promote Lint Rules

Use the batch promotion task instead of invoking just move-rule repeatedly.

Build the Manifest

Read the complete requirements. For a GitHub issue, read both its body and comments.
Verify every listed current rule exists under a crates/biome_*_analyze/src/lint/nursery/ directory.
Resolve incomplete or malformed requirements before editing. Do not infer missing group, recommendation, severity, or rename decisions from neighboring rows.
Create a temporary JSON file outside the repository, such as /tmp/biome-rule-promotions.json.

The top-level object maps each current lower-camel-case rule name to its final stable metadata:

json

{
  "noCurrentRule": {
    "group": "correctness",
    "recommended": true,
    "severity": "error",
    "newName": "noRenamedRule"
  },
  "useAnotherRule": {
    "group": "style",
    "recommended": false
  }
}

Fields:

group is required and must be a11y, complexity, correctness, performance, security, style, or suspicious.
recommended is optional. Include it when the requirements specify the final recommendation status; both true and false are meaningful.
severity is optional. Accepted values are info, warn, and error. Include it when the requirements specify a new final severity.
newName is optional. Omit it when the rule keeps its current name.

Use current names as object keys, even when newName is present. A rule implemented by multiple analyzers, such as matching JavaScript and HTML rules, needs only one entry.

Apply the Plan

Run the task once:

shell

just promote-rules /tmp/biome-rule-promotions.json

The task validates the complete manifest before moving files. It updates declarations, diagnostic categories, fixture option files, rule-option modules, and the migration rename table as applicable. It does not regenerate derived files or snapshots.

Inspect the move before generation:

shell

git status --short
git diff --stat

Confirm that every requested source file and fixture directory moved from nursery to its intended group. If a rule was renamed, search for stale occurrences of its old name and classify each occurrence before changing it; historical migration entries are expected to retain old names.

Show full SKILL.md (143 more words)Show less

Generate and Test

Load testing-codegen and run the required generators:

shell

just gen-rules
just gen-configuration
just gen-migrate

Run focused tests using each rule's final name. Review and accept pending snapshots individually according to testing-codegen; promotion snapshots must show the intended group and severity and must no longer contain the nursery notice.

Then run the analyzer crates affected by the manifest. If any rule was renamed, also run the biome_migrate tests and verify that configuration migration moves and renames the old key.

Run the repository-required checks:

shell

just f
just l

Run just lint-rules when rule documentation or suppression examples changed.

Release Entry and Cleanup

Rule promotion is user-facing and requires a minor changeset targeting next. Load changeset and describe the promoted groups, recommendation changes, severity changes, and renames that users need to know.

Delete the temporary manifest after the promotion is verified. Do not commit it unless the task explicitly requires a persistent promotion plan.

Files

Just SKILL.md in .claude/skills/promote-lint-rules of biomejs/biome.

Open the folder on GitHubat commit fd4df34

Compare with similar skills

Promote Lint Rules next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Promote Lint Rules compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Promote Lint Rules this skillbiomejs/biome	26k	—	~948	Automated safety check: Pass	Apache-2.0	yesterday
Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop	5.4k	—	~2.2k	Automated safety check: Pass	MIT	1 mo ago
Summarise Ecosystem Resultsastral-sh/ruff	50k	—	~2.2k	Automated safety check: Pass	MIT	today
Add Opik Code Quality Hookcomet-ml/opik	22k	—	~2.3k	Automated safety check: Pass	Apache-2.0	yesterday
Release Roundethereumjs/ethereumjs-monorepo	2.8k	—	~2k	Automated safety check: Pass	None	22 days ago
Ultraciteagustinusnathaniel/nextarter-tailwind	125	2 repos	~1.2k	Automated safety check: Pass	MIT	12 days ago

Similar skills

Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
5.4k GitHub stars~2.2k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
Summarise Ecosystem Results
astral-sh/ruff
Official
A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…
50k GitHub stars~2.2k tokensUpdated today
DevelopmentAuto-check passed
Add Opik Code Quality Hook
comet-ml/opik
Checklist for wiring a new linter into Opik's Code Quality pipeline: the four files to edit, the silent-failure gotchas and the pass/fail verification loop.
22k GitHub stars~2.3k tokensUpdated yesterday
DevelopmentAuto-check passed
Release Round
ethereumjs/ethereumjs-monorepo
Runs a coordinated EthereumJS npm release round in six human-gated phases — intent and readiness, CHANGELOG, version bump, publish (human executes), post-publish verification, and announcements.
2.8k GitHub stars~2k tokensUpdated 22 days ago
DevelopmentAuto-check passed
Ultracite
agustinusnathaniel/nextarter-tailwind
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects.
125 GitHub starsUsed in 2 repos~1.2k tokens
DevelopmentAuto-check passed
Mnemosyne Context
mnemosyne-oss/mnemosyne
Load this when working on the mnemosyne memory system — its repo, sync server, memory databases, or CI.
3.4k GitHub stars~2.6k tokensUpdated today
DevelopmentAuto-check passed

More from biomejs/biome

All 12 skills in this repo

Changeset
biomejs/biome
Official
A skill your agent uses 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.
26k GitHub stars~839 tokensUpdated yesterday
Auto-check passed
Doc Comments
biomejs/biome
Official
A skill your agent uses whenever writing or editing Rust //, ///, or //!
26k GitHub stars~3k tokensUpdated yesterday
Auto-check passed
Eslint Migrate Options
biomejs/biome
Official
A skill your agent uses when biome migrate eslint must preserve configurable ESLint rule options through source-option models, Biome conversions, typed rule variants, and migration fixtures.
26k GitHub stars~1.4k tokensUpdated yesterday
Auto-check passed
Formatter Development
biomejs/biome
Official
A skill your agent uses whenever implementing or debugging Biome formatter behavior, IR composition, node rules, layout selection, source-comment handling, verbatim formatting, idempotency, internal…
26k GitHub stars~2.1k tokensUpdated yesterday
Auto-check passed
Lint Rule Development
biomejs/biome
Official
A skill your agent uses when creating or modifying Biome lint rules or assists, including analyzer queries, semantic bindings, rule state, code actions, fix safety, options, registration, and…
26k GitHub stars~1.6k tokensUpdated yesterday
Auto-check passed
Parser Development
biomejs/biome
Official
A skill your agent uses when implementing or modifying Biome parser behavior, including .ungram grammars, lexers, token sources, parse rules, separated lists, error recovery, and parser fixtures.
26k GitHub stars~1.2k tokensUpdated yesterday
Auto-check passed

Works with

Questions about Promote Lint Rules

What does Promote Lint Rules do?

A skill your agent uses when promoting one or more Biome lint rules from nursery to stable groups, including promotion plans from GitHub issues, metadata changes, rule renames, generated…. Promote Lint Rules is an agent skill from biomejs/biome, published by the product's own GitHub organization. Use this skill when promoting one or more Biome lint rules from nursery to stable groups, including promotion plans from GitHub issues, metadata changes, rule renames, generated configuration, and promotion snapshots.

When should I use Promote Lint Rules?

Promote Lint Rules fits situations like: more Biome lint rules from nursery to stable groups; including promotion plans from GitHub issues; metadata changes; generated configuration.

How do I install Promote Lint Rules in Claude Code?

Run `npx skills add biomejs/biome --skill promote-lint-rules -a claude-code`. Or copy the skill folder (.claude/skills/promote-lint-rules in biomejs/biome) into .claude/skills/promote-lint-rules in your project. Claude Code loads it when a task matches its description.

How do I install Promote Lint Rules in Codex?

Run `npx skills add biomejs/biome --skill promote-lint-rules -a codex`. Or copy the skill folder (.claude/skills/promote-lint-rules in biomejs/biome) into .agents/skills/promote-lint-rules in your project. Codex loads it when a task matches its description.

Can I use Promote Lint Rules in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add biomejs/biome --skill promote-lint-rules -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/promote-lint-rules, .gemini/skills/promote-lint-rules, .github/skills/promote-lint-rules and .opencode/skills/promote-lint-rules in your project.

What does Promote Lint Rules need to run?

Going by SKILL.md and its folder, Promote Lint Rules needs the command-line tools its instructions call (just and git). Compatibility (from SKILL.md): Designed for coding agents working on the Biome codebase (github.com/biomejs/biome)..

Does Promote Lint Rules access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Promote Lint Rules safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Promote Lint Rules use?

Promote Lint Rules is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Promote Lint Rules use?

About 948 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Promote Lint Rules?

Skills that share tags, products or a category with Promote Lint Rules: Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.4k stars), Summarise Ecosystem Results (astral-sh/ruff, 50k stars), Add Opik Code Quality Hook (comet-ml/opik, 22k stars) and Release Round (ethereumjs/ethereumjs-monorepo, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Promote Lint Rules?

biomejs (a GitHub organization, an official publisher) maintains it in biomejs/biome, which has 25,916 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 10, 2026.

Source: biomejs/biome on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Promote Lint Rules

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

Promote Lint Rules

Build the Manifest

Apply the Plan

Generate and Test

Release Entry and Cleanup

Files

Compare with similar skills

Similar skills

More from biomejs/biome

Related

Questions about Promote Lint Rules