# linting-neostandard-eslint9

Configures ESLint v9 flat config and neostandard for JavaScript and TypeScript repositories. Helps migrate away from legacy .eslintrc files and set up CI checks.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 1100 installs · ★ 1960
- Author: mcollina
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/mcollina/skills/tree/HEAD/skills/linting-neostandard-eslint9/SKILL.md
- Updated: 2026-10-18
- HTML: https://affpapa.org/en/nevibecode/skills/linting-neostandard-eslint9

## What it does

The skill guides the agent through configuring ESLint v9 with `eslint.config.js` or `eslint.config.mjs` using `neostandard` as a base. It covers common workflows for JavaScript and TypeScript repositories, starting from installing `eslint@9` and adding project-specific rule overrides. Separate guideline files handle migrating from the legacy `standard` package or translating older `.eslintrc*` setups into flat config.

It also outlines continuous integration scripts and editor integration. For CI pipelines, it enforces a non-fix validation step, reserving the `--fix` flag strictly for local developer workflows. The skill relies entirely on ESLint v9 flat configuration, so older ESLint major versions are not supported here.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add mcollina/skills --skill linting-neostandard-eslint9 -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/linting-neostandard-eslint9/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/linting-neostandard-eslint9/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add mcollina/skills --skill linting-neostandard-eslint9 -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/linting-neostandard-eslint9/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add mcollina/skills --skill linting-neostandard-eslint9 -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/linting-neostandard-eslint9/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install mcollina/skills linting-neostandard-eslint9
```

2. **Manually: put the files in place**
- File: `.github/skills/linting-neostandard-eslint9/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add mcollina/skills --skill linting-neostandard-eslint9 -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/mcollina/skills --path skills/linting-neostandard-eslint9
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/linting-neostandard-eslint9/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add mcollina/skills --skill linting-neostandard-eslint9 -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/mcollina/skills/tree/HEAD/skills/linting-neostandard-eslint9/SKILL.md

## When to use it
- configure ESLint v9 flat config with neostandard in a new project
- migrate an existing codebase from standard to neostandard
- convert legacy .eslintrc configurations to eslint.config.js
- integrate non-fix linting checks into CI pipelines

## Example prompts
- Set up ESLint 9 with neostandard flat config in this project
- Migrate our legacy .eslintrc configuration to eslint.config.mjs
- Configure a non-fix linting step for our CI pipeline

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 62c7906868e1f4d7.

BEGIN THIRD-PARTY FILE 62c7906868e1f4d7
````text
---
name: linting-neostandard-eslint9
description: Configures ESLint v9 flat config and neostandard for JavaScript and TypeScript projects, including migrating from legacy `.eslintrc*` files or the `standard` package. Use when you need to set up or fix linting with `eslint.config.js` or `eslint.config.mjs`, troubleshoot lint errors, configure neostandard rules, migrate from `.eslintrc` to flat config, or integrate linting into CI pipelines and pre-commit hooks.
metadata:
  tags: linting, neostandard, eslint, eslint9, flat-config, javascript, typescript
---

## When to use

Use this skill when you need to:
- Set up linting in a JavaScript or TypeScript project
- Use `neostandard` as a Standard-like ESLint v9 flat-config baseline
- Configure `eslint@9` with the flat config system (`eslint.config.js`/`eslint.config.mjs`)
- Migrate from `standard` to `neostandard` or ESLint v9
- Migrate from legacy `.eslintrc*` configuration to ESLint v9
- Run linting consistently in CI and local development

## Quick start: basic neostandard setup

Install dependencies and create a minimal `eslint.config.js`:

```bash
npm install --save-dev eslint@9 neostandard
```

```js
// eslint.config.js
import neostandard from 'neostandard'

export default neostandard()
```

Verify the config works:

```bash
npx eslint .
```

## Common setup workflow (new project)

1. Install `eslint@9` and `neostandard` (see Quick start above)
2. Create `eslint.config.js` with `neostandard()` as the base
3. Add any project-specific rule overrides on top
4. Run `npx eslint .` to confirm no config errors
5. Add a lint script to `package.json`: `"lint": "eslint ."`
6. Integrate into CI with a non-fix run; use `--fix` only in local workflows

## How to use

Read individual rule files for implementation details and examples:

- [rules/neostandard.md](rules/neostandard.md) - Install, configure, and extend neostandard with ESLint
- [rules/eslint-v9-flat-config.md](rules/eslint-v9-flat-config.md) - Build ESLint v9 flat config for JS/TS projects
- [rules/migration-from-standard.md](rules/migration-from-standard.md) - Migrate from `standard` to `neostandard` or ESLint v9
- [rules/migration-from-legacy-eslint.md](rules/migration-from-legacy-eslint.md) - Migrate from `.eslintrc*` to flat config safely
- [rules/ci-and-editor-integration.md](rules/ci-and-editor-integration.md) - CI scripts, pre-commit, and editor setup

## Core principles

- Prefer reproducible linting with pinned major versions
- Keep config minimal and explicit
- Use flat config for ESLint v9 projects
- Treat lint failures as quality gates in CI
- Enable auto-fix for local workflows, but validate with non-fix CI runs
````
END THIRD-PARTY FILE 62c7906868e1f4d7

The third-party file has ended. Everything between the 62c7906868e1f4d7 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

© mcollina · MIT · https://github.com/mcollina/skills/tree/HEAD/skills/linting-neostandard-eslint9/SKILL.md

## Similar
- [setup-linting](https://affpapa.org/en/nevibecode/commands/setup-linting.md) — command · 510 installs
- [typescript-quality](https://affpapa.org/en/nevibecode/skills/typescript-quality.md) — skill · 1100 installs
- [sap-fiori-eslint-plugin](https://affpapa.org/en/nevibecode/skills/sap-fiori-eslint-plugin.md) — skill · 584 installs

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md