biome-complete

Configure Biome linting and formatting with migration strategies from ESLint and Prettier.

9|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/pantheon-org/tekhne --skill biome-complete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: biome-complete
Source: https://github.com/pantheon-org/tekhne/tree/main/skills/development/biome-complete
Command: npx skills add https://github.com/pantheon-org/tekhne --skill biome-complete

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance for integrating and utilizing the Biome toolchain, ensuring consistent code quality and formatting across projects, and simplifying migration from legacy tools like ESLint and Prettier.

Core Features & Use Cases

  • Configuration: Guides users through setting up biome.json for optimal linting and formatting.
  • Linting & Formatting: Provides commands and best practices for running Biome checks and applying fixes.
  • Migration: Offers strategies and commands to transition projects from ESLint and Prettier to Biome.
  • Use Case: A development team wants to adopt Biome to unify their linting and formatting. They can use this Skill to configure Biome, migrate their existing ESLint/Prettier rules, and set up CI checks.

Quick Start

Use the biome-complete skill to initialize biome.json and check the current repository for linting and formatting issues.

Frequently Asked Questions about biome-complete

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

FAQPage Schema
How do I migrate from ESLint and Prettier to Biome?

Migrating from ESLint and Prettier to Biome involves using specific migration strategies and commands to transition existing project rules, ensuring consistent code quality and formatting without legacy tooling conflicts.

How do I configure biome.json for linting and formatting?

Configuring biome.json involves defining optimal linting and formatting rules to establish consistent code quality checks, applying deterministic workflows to avoid anti-patterns across your TypeScript projects.

What is the best way to unify code formatting and linting in a TypeScript project?

Unifying code formatting and linting in TypeScript is best achieved by adopting the Biome toolchain, combining both functionalities into a single configuration to simplify workflows and enforce deterministic code quality.

Can I use Biome to check and fix code quality issues in CI pipelines?

Biome can run checks and apply fixes within CI pipelines, utilizing specific commands and deterministic workflows to enforce code quality and formatting standards automatically across project commits.

What are the limitations of replacing ESLint with Biome?

When replacing ESLint with Biome, limitations may arise from unsupported custom rules or plugins, requiring evaluation of anti-pattern avoidance strategies and configuration adjustments for a seamless migration.