migrate-oxlint

Migrate ESLint configurations to Oxlint with automatic config translation and plugin mapping.

2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/AmbitionsXXXV/Etyon --skill migrate-oxlint-ambitionsxxxv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-oxlint
Source: https://github.com/AmbitionsXXXV/Etyon/tree/main/.agents/skills/migrate-oxlint
Command: npx skills add https://github.com/AmbitionsXXXV/Etyon --skill migrate-oxlint-ambitionsxxxv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating an ESLint configuration to Oxlint to enable native Rust-based linting.

Core Features & Use Cases

  • Automated migration of ESLint configs to Oxlint (.oxlintrc.json).
  • Plugin mapping guidance and rule behavior adjustments for a smooth transition.
  • Review and customize generated config using available options such as --merge, --type-aware, and --details.

Quick Start

Run the migrate tool at the project root to generate an updated .oxlintrc.json and review the resulting configuration.

Frequently Asked Questions about migrate-oxlint

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

FAQPage Schema
How do I migrate ESLint configurations to Oxlint for JavaScript and TypeScript projects?

To migrate ESLint configurations to Oxlint, run the migration tool at your project root to automatically translate configs, map plugins, and generate an updated .oxlintrc.json file.

Does Oxlint support type-aware linting during the ESLint migration process?

Yes, Oxlint supports type-aware linting during migration by utilizing the --type-aware option to adjust rule behaviors appropriately for your JavaScript or TypeScript project.

What is the best way to translate custom ESLint plugins to an Oxlint configuration?

The best way to translate custom ESLint plugins is using the migration tool, which provides automated plugin mapping guidance and rule behavior adjustments for a smooth transition.

Can I merge existing Oxlint settings when migrating from ESLint?

Yes, you can merge existing settings when migrating from ESLint by using the --merge option, allowing you to review and customize the resulting configuration seamlessly.

Why does my Oxlint migration output need review after generating the .oxlintrc.json file?

Your Oxlint migration output needs review to ensure the automated config translation correctly adjusted rule behaviors, which you can verify using the --details option for transparency.