migrate-oxlint

Migrate ESLint configurations to Oxlint for JavaScript and TypeScript projects.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/SeanChenR/maestro-agent --skill migrate-oxlint-seanchenr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-oxlint
Source: https://github.com/SeanChenR/maestro-agent/tree/main/.agents/skills/migrate-oxlint
Command: npx skills add https://github.com/SeanChenR/maestro-agent --skill migrate-oxlint-seanchenr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the manual effort and risk involved in converting a JavaScript/TypeScript project's linting setup from ESLint to Oxlint by automating configuration translation, mapping common plugins, and highlighting rules that need manual attention.

Core Features & Use Cases

  • Automated Migration: Use the @oxlint/migrate tool to transform existing ESLint flat configs into a .oxlintrc.json and map popular plugins to their Oxlint equivalents.
  • Unmigrated Rule Guidance: Identify rules that could not be migrated automatically and recommend whether to keep ESLint for those rules, map them manually, or load them via jsPlugins.
  • Post-migration Actions: Advise on installing oxlint and optional packages (such as oxlint-tsgolint for type-aware rules), updating CI/scripts, handling local plugins, and switching formatter recommendations.

Quick Start

Run the migration tool from your project root with npx @oxlint/migrate, review the generated .oxlintrc.json, and then install oxlint and any recommended packages.

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 configs to Oxlint?

To migrate ESLint configs to Oxlint, run the @oxlint/migrate tool from your project root via npx. This automatically transforms your existing ESLint flat configs into a .oxlintrc.json file and maps popular plugins to their Oxlint equivalents.

Can I migrate ESLint to Oxlint in a monorepo?

Yes, you can migrate ESLint to Oxlint in a monorepo. The migration tool supports converting linting setups for both single-repo projects and monorepos, handling configuration translation and plugin mapping across the workspace.

What happens to ESLint rules that cannot be migrated automatically?

Unmigrated ESLint rules are reported by the tool for manual attention. It advises whether to keep ESLint for those rules, map them manually, or load them into Oxlint via jsPlugins for untranslatable plugins.

Do I need to install additional packages for type-aware Oxlint rules?

Yes, you need to install oxlint-tsgolint for type-aware rules. The migration tool recommends installing this package alongside oxlint when your configuration requires type-aware linting capabilities.

What post-migration steps are required after converting ESLint to Oxlint?

Post-migration steps include installing oxlint and recommended packages, updating CI pipelines and editor integrations, handling local plugins, and switching formatter recommendations to complete the transition from ESLint.