biome-v2

Lint, format, and organize imports in JavaScript/TypeScript projects via Biome CLI.

7|4|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/nklisch/skills --skill biome-v2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: biome-v2
Source: https://github.com/nklisch/skills/tree/main/.agents/skills/biome-v2
Command: npx skills add https://github.com/nklisch/skills --skill biome-v2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often struggle with maintaining consistent code style, catching lint errors, and keeping imports tidy across JavaScript/TypeScript projects. Biome v2 provides a unified tool that handles linting, formatting, and import organization based on a single configuration file.

Core Features & Use Cases

  • Comprehensive Linting & Formatting: Enforces style rules, detects unused variables, and applies automatic fixes with biome check --write.
  • Import Organization: Automatically sorts and groups imports on save.
  • CI‑Ready Mode: Fast, read‑only checks for continuous integration pipelines.
  • VCS Integration & Overrides: Respects .gitignore, allows per‑pattern rule overrides, and filters files by status.

Quick Start

Use the biome skill to lint, format, and organize imports for the current repository.

Frequently Asked Questions about biome-v2

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

FAQPage Schema
How do I lint and format JavaScript and TypeScript code automatically?

You can lint and format JavaScript and TypeScript code by running the Biome CLI with a biome.json configuration file, using the --write flag to apply automatic fixes for style and unused variables.

What's the best way to organize imports in a TypeScript project?

Organizing imports in a TypeScript project is handled by configuring Biome v2 to automatically sort and group imports on save based on your centralized biome.json settings.

Do I need a biome.json file to run linting checks?

Yes, a biome.json file is required to define the style, linting rules, and CI checks that the Biome CLI enforces across your source directories.

Can I use Biome for read-only checks in a CI pipeline?

Yes, Biome supports a CI-ready mode that performs fast, read-only checks without applying fixes, allowing you to validate code style and linting rules in continuous integration pipelines.

Does Biome respect .gitignore and allow per-pattern rule overrides?

Biome respects .gitignore for file filtering and supports per-pattern rule overrides, allowing you to apply specific linting and formatting configurations to different file patterns.