eslint-migrate-options
This skill guides you through building option migrators for the `biome migrate eslint` command, preserving ESLint rule configurations beyond severity alone. Learn to model ESLint options in Rust, convert them to Biome equivalents, wire typed rule variants into the migration pipeline, and test through fixture-driven specs.
eslint-migrate-options helps you implement custom ESLint-to-Biome rule option migrators with typed deserialization.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-27
eslint-migrate-options helps you implement custom ESLint-to-Biome rule option migrators with typed deserialization. This skill guides you through building option migrators for the `biome migrate eslint` command, preserving ESLint rule configurations beyond severity alone. Learn to model ESLint options in Rust, convert them to Biome equivalents, wire typed rule variants into the migration pipeline, and test through fixture-driven specs.
Use it when
- eslint-migrate-options covers mapping ESLint plugin rule options to Biome configuration semantics.
- eslint-migrate-options guides you through adding typed Rule variants and wiring migrators into the conversion pipeline.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
biomejs/biome/eslint-migrate-options · repository language: Rust
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How to migrate eslint rule options to biome?
eslint-migrate-options teaches you to build custom migrators that convert ESLint rule options into Biome configuration semantics. You define Rust structs to deserialize ESLint options, implement conversion logic to map them to Biome equivalents, and integrate typed Rule variants into the `biome migrate eslint` pipeline. This preserves rule behavior beyond severity alone, ensuring your ESLint configurations translate faithfully.
What does eslint-migrate-options cover for rule mapping?
eslint-migrate-options covers mapping ESLint plugin rule options to Biome configuration semantics. You'll learn to model option structures in Rust, deserialize them with typed deserialization, implement migrators that translate option values, and wire those migrators into the conversion pipeline. The skill includes fixture-driven snapshot tests to validate that ESLint options migrate correctly.
How do I implement eslint rule migrator in biome codebase?
eslint-migrate-options guides you through adding typed Rule variants and wiring migrators into the conversion pipeline. You create Rust structs representing ESLint rule options, implement deserialization logic, build migrator functions that transform those options to Biome equivalents, and integrate them into the `biome migrate eslint` command. Testing uses fixture-driven snapshot specs to ensure correctness.
Can eslint-migrate-options handle plugin-specific rules?
Yes. eslint-migrate-options shows how to preserve ESLint rule behavior during `biome migrate eslint` conversion, including plugin-specific rules like eslint-plugin-unicorn, typescript-eslint, and jsx-a11y. You model each plugin's option structures, implement custom migrators for their semantics, and test through fixture-driven snapshots to validate that plugin rules and their options convert accurately.
What testing approach does eslint-migrate-options recommend?
eslint-migrate-options recommends fixture-driven snapshot tests to validate ESLint option migration. You define test fixtures with ESLint configurations, run them through the migrator, and compare snapshots of the resulting Biome configuration. This approach ensures that rule severity, custom options, and plugin-specific settings all migrate correctly and consistently.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Purpose
Use this skill when a Biome lint rule already exists and biome migrate eslint should preserve more than just the rule severity.
This skill is specifically for cases where an ESLint rule has options that need to be:
- deserialized from ESLint config
- translated into Biome rule options
- wired into the migrate pipeline
- tested through migrator spec fixtures without depending on CLI tests
Do not use this skill for severity-only migrations. Those are usually covered by the generated rule mapping in eslint_any_rule_to_biome.rs.
Before You Edit
Confirm these points first:
- The target Biome rule already exists and already has its own options type in
crates/biome_rule_options/src/. - The
(truncated - see the full file via the links below)
File tree — 1 file
.claude/skills/eslint-migrate-options/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Implement custom ESLint-to-Biome rule option migrators with typed deserialization”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
testing-codegen guides you through snapshot testing with insta and code generation for the Biome codebase. It covers running tests for specific crates, fast iteration with quick-test workflows, and safely managing snapshots—including pruning orphaned files and reviewing changes interactively. Use this skill when testing lint rules, inspecting AST structure, or regenerating parser and analyzer code.
This skill guides you through building new lint rules and assist actions for Biome. It covers rule scaffolding across multiple languages, implementation patterns with semantic analysis, code action setup, and the three-pillar diagnostic framework required for all rules. Use it when adding custom rules like noVar or useConst to Biome's codebase.
Ultracite unifies linting and formatting through multiple providers—Biome (default), ESLint+Prettier, or Oxlint—delivering framework-specific presets and sensible defaults out of the box. It replaces traditional multi-tool setups with a single, faster solution optimized for React, Next.js, Vue, Svelte, and other modern frameworks. Includes Git hook integration, AI editor support, and migration tooling for upgrading from legacy configurations.
Biome combines linting and formatting into one Rust-powered tool designed for JavaScript and TypeScript projects. It eliminates the need for separate ESLint and Prettier setups while delivering dramatically faster performance and sensible defaults out of the box.
Biome Validator checks your Biome configuration for version compatibility, proper schema setup, and modern linting rules. It flags deprecated patterns and guides migration from ESLint, helping you audit existing projects or set up linting from scratch.
Linter Formatter Init automates code quality setup for JavaScript and TypeScript projects, installing Biome (default) or ESLint + Prettier alongside Vitest testing and Husky pre-commit hooks. The skill configures VS Code integration, generates bun scripts for linting and formatting, and supports monorepo layouts.
More skills doc-comments (Apache-2.0) · biome (MIT) · formatter-development (Apache-2.0) · diagnostics-development (Apache-2.0) · pull-request (Apache-2.0)