Oxlint

Use this skill when work touches Oxlint or Oxc linting: install/config, day-to-day usage, rules/plugins, type-aware linting, ESLint coexistence or migration, editors, or CI.

Workflow

1. Inspect the local Oxlint surface before changing code:
   • Package versions for oxlint, optional oxlint-tsgolint, eslint-plugin-oxlint, @oxlint/migrate.
   • Config: prefer oxlint.config.ts / .mts with defineConfig; also accept .oxlintrc.json(c) (one type per directory).
   • Remaining ESLint setup, ignore files, scripts (lint / lint:fix), and editor Oxc settings.
   • Whether type-aware linting or JS plugins are in play.
2. For setup, how-to, progressive adoption, diagnostics loops, baselines, or troubleshooting, follow the full guide first: usage-guide.md.
3. Refresh current official docs when versions differ from the snapshot or the work touches type-aware, JS plugins, or migration. Start from source-map.md.
4. Route deeper detail to the focused references:
   • Install, CLI, config shape, nested configs, ignores: setup-cli-config.md.
   • Categories, plugins, rules, inline ignores, type-aware: rules-plugins-typeaware.md.
   • ESLint coexistence, migration, editors, CI: eslint-ci-editors.md.
5. Preserve the repository's existing lint severity and plugin choices unless the user asks to migrate or expand coverage.
6. Verify with the narrowest useful bunx oxlint / bun run lint invocation.