Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    ESLint Flat Config Migration to ESLint 10 with Parity Check

    1

    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

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    ESLint Flat Config Migration to ESLint 10 with Parity Check

    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

    CheckBeforeAfterStatus
    Files linted418418Same
    Enabled rules (src/app/page.tsx)192195+3 explained
    Problems2734+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

    RuleChangeCauseAction
    no-useless-assignmentnew, 4 problemsadded to eslint:recommended in v10fix (real dead writes)
    no-unassigned-varsnew, 0 problemsadded to eslint:recommended in v10keep
    preserve-caught-errornew, 3 problemsadded to eslint:recommended in v10your call
    react/jsx-uses-varsremovednot needed: ESLint 10 tracks JSX referencesremoved

    Plugins

    PluginNative flat config?How loaded
    typescript-eslintYestseslint.configs.recommended
    eslint-plugin-reactYesreact.configs.flat.recommended
    eslint-plugin-react-hooksYes (upgraded)flat preset from the installed version's README
    eslint-plugin-jsx-a11yYesjsxA11y.flatConfigs.recommended
    eslint-plugin-importYesimportPlugin.flatConfigs.recommended
    eslint-config-prettierPlain objectplaced last

    Still to do

    • preserve-caught-error: 3 catch blocks rethrow without cause. Fix, or turn the rule off on purpose?
    • CI: drop --ext .ts,.tsx from .github/workflows/lint.yml so files patterns in the config are the single source of truth.
    • Old .eslintrc.json files renamed to .bak after your yes.

    Verdict is PARTIAL until the preserve-caught-error decision and the CI change are done.

    page.tsx

    TSX · React component

    Generated

    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.json eslintConfig, nested configs, .eslintignore, /* eslint-env */ comments, --ext and --rulesdir in scripts and CI
    • Captures a baseline before touching anything: --print-config for representative files and a full JSON lint result
    • Drafts the new config with @eslint/migrate-config, then replaces FlatCompat with native plugin exports wherever they exist
    • Maps env, globals, parser, overrides, excludedFiles and ignorePatterns correctly, and catches the common silent losses (missing extensions, scoped vs global ignores, 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-env comments now errors, radix and no-shadow-restricted-names changes
    • 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.

    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. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    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

    Requires

    @eslint/migrate-config
    Node.js
    eslint
    Git

    Permissions

    Terminal / Shell
    Listed29 days ago

    What's inside

    Frequently Asked Questions

    Before changing anything it captures a baseline: --print-config for representative files and a full JSON lint result. After the migration it runs the same commands and compares the files linted, the enabled rules and severities, and the problem counts by rule. Every difference is listed with its cause, and you decide whether to keep or restore it.

    The skill is compatible with any AI agent that has file system and terminal access, and it supports projects running ESLint versions 8, 9, and 10 across JavaScript, TypeScript, and popular frameworks like React and Vue.

    A plain prompt rewrites the config and stops. This skill compares before and after evidence, catches the common silent losses (TypeScript files no longer linted, ignores that became local, presets in the wrong order), and only gives the MIGRATED verdict when every difference is explained. If it could not capture a baseline, it says so.

    Yes, the skill is designed to handle monorepo architectures by consolidating scattered configuration files and converting legacy `env` settings and `.eslintignore` files into modern `languageOptions` and `globalIgnores` syntax.

    A SKILL.md with the full migration procedure and verdict rules, plus a reference file of ESLint 9 and 10 facts checked against the official migration guides: removed options, the eslintrc to flat config mapping, helper tools and common plugin notes.

    You will need a clean Git working tree and a functional Node.js environment where your current ESLint version can still execute to allow the skill to generate accurate baseline comparison reports.

    New in Code Quality & Review