Configure and run Biome v2 linting, formatting, and import organizing for JavaScript and TypeScript projects.
npx skills add https://github.com/bm629/agent-skills --skill biome-bm629
Please help me install this Agent Skill. Skill: biome Source: https://github.com/bm629/agent-skills/tree/main/skills/biome Command: npx skills add https://github.com/bm629/agent-skills --skill biome-bm629
--apply) causes errors against the current v2 CLI. This Skill provides verified, up-to-date guidance for replacing that stack with Biome, the single Rust-based tool that lints, formats, and organizes imports. ## Core Features & Use Cases - Install and configure Biome v2: Install @biomejs/biome, scaffold biome.json, and set formatter, linter rule groups, assist-based import organizing, VCS integration, overrides, and monorepo extends/root configs. - Correct CLI and CI usage: Run biome check --write locally and biome ci as a read-only CI gate, avoiding the removed v1 --apply flags. - Migration and custom rules: Port existing ESLint/Prettier configs with biome migrate, and author custom lint rules as GritQL plugins. - Use Case: You inherit a project running ESLint + Prettier and want one fast tool. Use this Skill to migrate both configs into a single biome.json, then wire biome ci into your CI pipeline as the lint/format gate. ## Quick Start Use the biome skill to set up Biome v2 linting and formatting in my TypeScript project and add a CI check.High-intent search queries and answers about installing and using this skill.
Install with npm install --save-dev --save-exact @biomejs/biome, then run npx biome init to scaffold biome.json. Enable the formatter, recommended linter rules, and assist.actions.source.organizeImports, then run npx biome check --write to apply safe fixes.
Biome replaces both ESLint and Prettier with one Rust binary and one biome.json config, covering linting, formatting, and import sorting. Run biome migrate eslint --write and biome migrate prettier --write to port existing configs, then remove the old tools to avoid double tooling.
The --apply and --apply-unsafe flags were removed in Biome v2. Use biome check --write for safe fixes and biome check --write --unsafe to also apply unsafe fixes; --fix is an alias of --write.
Use npx biome ci . as the CI gate. It runs format, lint, and import-sort checks in read-only mode and never writes to the tree, unlike biome check --write which mutates files and should only run locally.
In v2, import organizing moved from the top-level organizeImports key to an assist action. Set assist.actions.source.organizeImports to "on" in biome.json; a v1-shaped config silently skips import organizing.
Yes, Biome v2 supports custom rules as GritQL plugins registered under the plugins key in biome.json as .grit files. Plugins currently target JavaScript and CSS only, and you should prefer a built-in rule from the rule groups when one covers your case.
zhangyu1818Configure ESLint for JavaScript/TypeScript projects with detected presets.
gengirishConfigures Biome linting and formatting plus tsx TypeScript script execution for monorepo projects.
Chai-UnRun formatting, linting, type checks, and tests before commits.
1Mangesh1Generate ESLint, Prettier, Ruff, Black, mypy, EditorConfig, and pre-commit configuration files.