- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add aiskillstore/marketplace --skill oxlint -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add aiskillstore/marketplace --skill oxlint -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add aiskillstore/marketplace --skill oxlint -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add aiskillstore/marketplace --skill oxlint -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/aiskillstore/marketplace/tree/HEAD/pending/delexw/oxlintVom Herausgeber
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.
Before linting, confirm the project uses oxlint by checking for any of:
oxlint in package.json devDependencies/dependencies.oxlintrc.json file in the project rootoxlint.config.ts file in the project rootoxlint or lint script in package.json that references oxlintIf none of these exist, the project doesn't use oxlint — don't run it.
Run oxlint to check your work. Prefer the project's npm script if one exists:
# If package.json has a lint script using oxlint
npm run lint
# Otherwise, run directly
npx oxlint
npx oxlint --fix
Use --fix for safe automatic fixes. Avoid --fix-dangerously unless the user explicitly asks for it — it can apply unsafe transformations.
After editing only a few files, you can lint just those:
npx oxlint src/components/Button.tsx src/utils/helpers.ts
Oxlint prints diagnostics with rule names in parentheses, e.g. (no-unused-vars). When fixing:
// oxlint-ignore comments as a last resort when the diagnostic is a genuine false positiveFor CI or tooling integration:
npx oxlint --format json # Machine-readable JSON
npx oxlint --format github # GitHub Actions annotations
npx oxlint --format unix # Simple one-line-per-error format
npx oxlint --init
This generates an .oxlintrc.json starter config.
The config uses JSONC (JSON with comments). Key sections:
{
// 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
"pedantic": "off", // Opinionated style checks
"perf": "warn", // Performance anti-patterns
"style": "off", // Cosmetic preferences
"restriction": "off", // Extra-strict rules (opt-in)
"nursery": "off" // Unstable/experimental rules
},
// Plugins to enable (setting this overwrites defaults, so list all you want)
"plugins": ["typescript", "unicorn", "oxc"],
// File-specific overrides
"overrides": [
{
"files": ["**/*.test.{ts,tsx}"],
"rules": { "no-console": "off" }
},
{
"files": ["scripts/**"],
"rules": { "no-console": "off" }
}
],
// Environment globals
"env": {
"browser": true,
"node": true
},
// Plugin-wide settings
"settings": {
"react": {
"linkComponents": [{ "name": "Link", "linkAttribute": "to" }]
},
"jsx-a11y": {
"components": { "Link": "a", "Button": "button" }
}
},
// Type-aware linting (requires tsconfig)
"options": {
"typeAware": true
}
}
"off" / "allow" — Disable the rule"warn" — Report but don't fail the build"error" / "deny" — Report and exit non-zeroUnique rule names can omit plugin prefix: "no-console" = "eslint/no-console".
Categories group rules by intent. The recommended starting point:
correctness: "error" — Always on. Catches real bugs.suspicious: "warn" — Good signal, occasionally noisy.Enabled by default: typescript, unicorn, oxc
Opt-in (CLI flags or config):
To disable a default plugin: --disable-typescript-plugin, --disable-unicorn-plugin, --disable-oxc-plugin.
{
"extends": ["./configs/base.json", "./configs/frontend.json"]
}
Later entries override earlier ones. Paths resolve relative to the declaring config.
Oxlint supports nested configs. Each directory can have its own .oxlintrc.json that overrides parent settings. Disable with --disable-nested-config if unwanted.
Categories can also be used with -A/-W/-D:
npx oxlint -D correctness -W suspicious -A pedantic
// oxlint-ignore no-console -- needed for debug logging
console.log(debugInfo);
// oxlint-ignore-next-line no-unused-vars
const _placeholder = computeValue();
Use oxlint-ignore (not eslint-disable) — oxlint recognizes both, but prefer its native syntax.
If the project is moving from ESLint to oxlint:
Side-by-side approach — Run both linters, with eslint-plugin-oxlint disabling rules that oxlint already covers:
npm install -D eslint-plugin-oxlint
Add it as the last plugin in your ESLint config.
Full replacement — Use @oxlint/migrate to convert your ESLint config:
npx @oxlint/migrate
This generates an .oxlintrc.json from your existing ESLint configuration.
.js, .mjs, .cjs, .ts, .mts, .cts, .jsx, .tsx, .vue, .svelte, .astro
For .vue, .svelte, and .astro files, oxlint lints only the <script> blocks.
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`
---name: oxlintdescription: Run and configure oxlint — the high-performance JavaScript/TypeScript linter built on the Oxc compiler stack…---# pending/delexw/oxlint/SKILL.mdÜbersicht
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.
FAQ
Laden Sie pending/delexw/oxlint/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/aiskillstore/marketplace.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.