# oxlint

A skill for Claude Code that runs oxlint and configures its rules. Activates when oxlint is listed in package.json or config files exist in the project root.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 1000 installs · ★ 2 repo stars
- Author: delexw
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/delexw/claude-code-misc/tree/HEAD/skills/oxlint/SKILL.md
- Updated: 2026-03-28
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/oxlint

## What it does

The skill runs linting on JavaScript and TypeScript files using oxlint on top of the Oxc compiler stack, using over 690 rules from ESLint and TypeScript collections. The agent first inspects `package.json` dependencies or looks for `.oxlintrc.json` and `oxlint.config.ts`. If no oxlint configuration exists, the agent aborts execution.

Linting executes via `npx oxlint` or existing project scripts. Safe automated corrections apply through `--fix`, while `--fix-dangerously` remains disabled unless specifically requested. Output can be structured as `json`, `github`, or `unix` for CI pipelines.

Enabling type-aware rules via `--type-aware` requires an active `tsconfig.json` in the project root.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add delexw/claude-code-misc --skill oxlint -a claude-code
```

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

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add delexw/claude-code-misc --skill oxlint -a codex
```

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

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add delexw/claude-code-misc --skill oxlint -a cursor
```

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

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install delexw/claude-code-misc skills/oxlint
```

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

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add delexw/claude-code-misc --skill oxlint -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/delexw/claude-code-misc --path skills/oxlint
```

### Windsurf (Devin Desktop)

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

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add delexw/claude-code-misc --skill oxlint -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/delexw/claude-code-misc/tree/HEAD/skills/oxlint/SKILL.md

## When to use it
- lint JavaScript and TypeScript files with oxlint
- apply safe automatic corrections using `--fix`
- generate a starter `.oxlintrc.json` configuration file
- activate optional plugins such as React or Next.js

## Example prompts
- Run oxlint on the project and fix safe issues
- Generate an .oxlintrc.json file with React rules enabled
- Lint only the modified files inside src/components

## 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: 9c9c160bc704a4f8.

BEGIN THIRD-PARTY FILE 9c9c160bc704a4f8
````text
---
name: oxlint
description: "Run and configure oxlint — the high-performance JavaScript/TypeScript linter built on the Oxc compiler stack. Use this skill whenever working in a project that has oxlint installed (check for `oxlint` in package.json devDependencies or an `.oxlintrc.json` / `oxlint.config.ts` config file). This includes when you need to lint code after making changes, fix linting errors, configure oxlint rules/plugins, set up or modify `.oxlintrc.json`, or migrate from ESLint."
---

# Oxlint — High-Performance JS/TS Linter

Oxlint is 50-100x faster than ESLint. It ships with 690+ rules covering ESLint core, TypeScript, React, Jest, Unicorn, jsx-a11y, and more. It prioritizes high-signal correctness checks by default — things that are incorrect, unsafe, or useless — so teams can adopt it without drowning in false positives.

## Detection

Before linting, confirm the project uses oxlint by checking for any of:
- `oxlint` in `package.json` devDependencies/dependencies
- An `.oxlintrc.json` file in the project root
- An `oxlint.config.ts` file in the project root
- An `oxlint` or `lint` script in `package.json` that references `oxlint`

If none of these exist, the project doesn't use oxlint — don't run it.

## Running Oxlint

### After code changes
Run oxlint to check your work. Prefer the project's npm script if one exists:

```bash
# If package.json has a lint script using oxlint
npm run lint

# Otherwise, run directly
npx oxlint
```

### Fixing issues automatically
```bash
npx oxlint --fix
```

Use `--fix` for safe automatic fixes. Avoid `--fix-dangerously` unless the user explicitly asks for it — it can apply unsafe transformations.

### Linting specific files
After editing only a few files, you can lint just those:
```bash
npx oxlint src/components/Button.tsx src/utils/helpers.ts
```

### Interpreting output
Oxlint prints diagnostics with rule names in parentheses, e.g. `(no-unused-vars)`. When fixing:
1. Read the diagnostic message carefully — oxlint gives precise, actionable information
2. Fix the underlying code issue rather than suppressing the rule
3. Only add `// oxlint-ignore` comments as a last resort when the diagnostic is a genuine false positive

### Output formats
For CI or tooling integration:
```bash
npx oxlint --format json        # Machine-readable JSON
npx oxlint --format github      # GitHub Actions annotations
npx oxlint --format unix        # Simple one-line-per-error format
```

## Configuration

### Creating a config
```bash
npx oxlint --init
```
This generates an `.oxlintrc.json` starter config.

### Config file format (.oxlintrc.json)
The config uses JSONC (JSON with comments). Key sections:

```jsonc
{
  // Enable/disable individual rules with severity levels
  "rules": {
    "no-unused-vars": "error",
    "no-console": "warn",
    "no-plusplus": ["error", { "allowForLoopAfterthoughts": true }]
  },

  // Enable groups of related rules by category
  "categories": {
    "correctness": "error",   // Definitely-wrong code
    "suspicious": "warn",     // Probably-wrong code
````
END THIRD-PARTY FILE 9c9c160bc704a4f8

The third-party file has ended. Everything between the 9c9c160bc704a4f8 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.

First 3079 of 7934 bytes. © delexw · MIT · https://github.com/delexw/claude-code-misc/tree/HEAD/skills/oxlint/SKILL.md

_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
