migrate-oxlint

Migrate ESLint configurations to Oxlint using @oxlint/migrate and generate .oxlintrc.json.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/JoeyMckenzie/website-laravel --skill migrate-oxlint-joeymckenzie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-oxlint
Source: https://github.com/JoeyMckenzie/website-laravel/tree/main/.agents/skills/migrate-oxlint
Command: npx skills add https://github.com/JoeyMckenzie/website-laravel --skill migrate-oxlint-joeymckenzie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams migrate linting from ESLint to Oxlint, reducing manual reconfiguration and potential compatibility issues.

Core Features & Use Cases

  • Automated migration using the official @oxlint/migrate tool to generate a ready-to-use .oxlintrc.json from an ESLint config.
  • Clear guidance on plugin mapping, rule categories, and post-migration checks to ensure parity.
  • Use Case: Teams adopting Oxlint mid-project can migrate CI lint steps with minimal downtime and predictable results.

Quick Start

Run the migration tool in your project root to generate the .oxlintrc.json from your ESLint config.

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?

Migrate ESLint configurations to Oxlint by running the official @oxlint/migrate tool in your project root to generate a ready-to-use .oxlintrc.json file. You then review the generated config and optionally install oxlint packages.

Can I migrate ESLint to Oxlint for JavaScript and TypeScript projects?

Yes, you can migrate ESLint to Oxlint for JavaScript and TypeScript projects. The migration process maps common ESLint plugins to Oxlint equivalents and guides post-migration checks to ensure rule parity across your codebase.

What is the best way to unify linting tools and improve performance?

Unify linting and improve performance by migrating from ESLint to Oxlint. This tool-based migration reduces manual reconfiguration, unifies your linting step, and provides predictable results with minimal CI downtime.

Does Oxlint work with common ESLint plugins?

Oxlint provides plugin mapping for common ESLint plugins during migration. The Skill guides you through mapping rule categories and reviewing the generated configuration to maintain compatibility and enforce parity.

What should I check after running an ESLint to Oxlint migration?

After running the ESLint to Oxlint migration, review the generated .oxlintrc.json file to verify plugin mappings and rule categories. You should also install oxlint and related packages, then run post-migration checks.

Why migrate to Oxlint instead of keeping existing ESLint configs?

Migrate to Oxlint to achieve faster linting performance and unify your tooling. The automated migration reduces manual reconfiguration effort and resolves potential compatibility issues when adopting Oxlint mid-project.