- Home
- Skills
- Code Quality & Review
- ESLint Flat Config Migration to ESLint 10 with Parity Check
Works with the AI Agents you already use
ESLint Flat Config Migration to ESLint 10 with Parity Check
Migrate .eslintrc to eslint.config.js and upgrade to ESLint 10 without silently losing rules, files or plugins. Before/after parity proof. MIGRATED / PARTIAL / BLOCKED.
$5
ESLint Flat Config Migration to ESLint 10 with Parity Check
Example session with this skill installed
Move our Next.js + TypeScript repo from .eslintrc.json to flat config and ESLint 10. We use typescript-eslint, react, react-hooks, jsx-a11y, import and prettier. Lint is run with eslint . --ext .ts,.tsx in CI. Don't lose any rules.
- Read your context and instructions
- Compiled the eslint flat config
- Generated the UI component
ESLint migration: web-app — VERDICT: PARTIAL
Summary
ESLint 8.57 → 10.x, Node 22.14 (meets the 22.13+ minimum). 3 config sources (.eslintrc.json, src/legacy/.eslintrc.json, .eslintignore) merged into eslint.config.mjs.
Parity evidence
| Check | Before | After | Status |
|---|---|---|---|
| Files linted | 418 | 418 | Same |
| Enabled rules (src/app/page.tsx) | 192 | 195 | +3 explained |
| Problems | 27 | 34 | +7 explained |
First draft linted only 141 files: files matched **/*.js and dropped every .ts/.tsx file that --ext used to cover. Fixed with files: ["**/*.{ts,tsx,mts,cts}"].
Rule and result differences
| Rule | Change | Cause | Action |
|---|---|---|---|
| no-useless-assignment | new, 4 problems | added to eslint:recommended in v10 | fix (real dead writes) |
| no-unassigned-vars | new, 0 problems | added to eslint:recommended in v10 | keep |
| preserve-caught-error | new, 3 problems | added to eslint:recommended in v10 | your call |
| react/jsx-uses-vars | removed | not needed: ESLint 10 tracks JSX references | removed |
Plugins
| Plugin | Native flat config? | How loaded |
|---|---|---|
| typescript-eslint | Yes | tseslint.configs.recommended |
| eslint-plugin-react | Yes | react.configs.flat.recommended |
| eslint-plugin-react-hooks | Yes (upgraded) | flat preset from the installed version's README |
| eslint-plugin-jsx-a11y | Yes | jsxA11y.flatConfigs.recommended |
| eslint-plugin-import | Yes | importPlugin.flatConfigs.recommended |
| eslint-config-prettier | Plain object | placed last |
Still to do
preserve-caught-error: 3 catch blocks rethrow withoutcause. Fix, or turn the rule off on purpose?- CI: drop
--ext .ts,.tsxfrom.github/workflows/lint.ymlsofilespatterns in the config are the single source of truth. - Old
.eslintrc.jsonfiles renamed to.bakafter your yes.
Verdict is PARTIAL until the preserve-caught-error decision and the CI change are done.
page.tsx
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
ESLint 10 removed .eslintrc support completely, and ESLint 9 reached end of life in August 2026. Most migrations "work" on the first try, then quietly stop linting .ts files, drop an overrides block, or turn a global ignore into a local one. Nobody notices until bad code ships.
This skill gives your coding agent a fixed procedure and a reference file checked against the official ESLint migration guides. It:
- Inventories every config source:
.eslintrc*,package.jsoneslintConfig, nested configs,.eslintignore,/* eslint-env */comments,--extand--rulesdirin scripts and CI - Captures a baseline before touching anything:
--print-configfor representative files and a full JSON lint result - Drafts the new config with
@eslint/migrate-config, then replacesFlatCompatwith native plugin exports wherever they exist - Maps
env,globals,parser,overrides,excludedFilesandignorePatternscorrectly, and catches the common silent losses (missing extensions, scoped vs globalignores, wrong preset order) - Handles the ESLint 10 changes: Node 20.19+ / 22.13+ / 24+, config lookup from each file's folder, new recommended rules, JSX reference tracking,
eslint-envcomments now errors,radixandno-shadow-restricted-nameschanges - Proves parity: same files linted, rule-by-rule severity diff, problem counts by rule, every difference explained
- Returns a report and a verdict: MIGRATED, PARTIAL or BLOCKED
Who it is for: teams on ESLint 8 or 9 that need to move to flat config or ESLint 10, monorepo maintainers with several configs, and anyone whose lint results changed after an upgrade.
Safety: works on a clean branch, never deletes the old config until parity is proven and you agree, never disables rules or adds eslint-disable comments to make lint pass, and asks before installing packages.
Honesty note: it only reports commands it actually ran. If no baseline could be captured, it says so and will not give MIGRATED.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.
Requires clean git status. Parity verification requires the baseline ESLint version to be runnable. Cannot reach MIGRATED status if no baseline evidence can be captured.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 29 days ago
- Software
- @eslint/migrate-config
Node.jseslint
Git