Install any skill in seconds. Free to start, no credit card required.
Get Started Free →migrate-oxlint
Guide for migrating a project from ESLint to Oxlint.
Passed 11 of 22 test cases with the skill, and 2 of 22 without it.
9 fixed2 passed either way11 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
The instructions your model reads when the skill loads.
This skill guides you through migrating a JavaScript/TypeScript project from ESLint to Oxlint.
Oxlint is a high-performance linter that implements many popular ESLint rules natively in Rust. It can be used alongside ESLint or as a full replacement.
An official migration tool is available, and will be used by this skill: @oxlint/migrate
Run the migration tool in the project root:
npx @oxlint/migrate
This reads your ESLint flat config (eslint.config.js for example) and generates a .oxlintrc.json file from it. It will find your ESLint config file automatically in most cases.
See options below for more info.
| Option | Description |
|---|---|
--type-aware | Include type-aware rules from @typescript-eslint (will require the oxlint-tsgolint package to be installed after migrating) |
--with-nursery | Include experimental rules still under development, may not be fully stable or consistent with ESLint equivalents |
--js-plugins [bool] | Enable/disable ESLint plugin migration via jsPlugins (default: enabled) |
--details | List rules that could not be migrated |
--replace-eslint-comments | Convert all // eslint-disable comments to // oxlint-disable |
--output-file <file> | Specify a different output path (default: .oxlintrc.json) |
If your ESLint config is not at the default location, pass the path explicitly:
npx @oxlint/migrate ./path/to/eslint.config.js
After migration, review the generated .oxlintrc.json.
test cases passed, vs 2 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.