oxlint

Automate JavaScript and TypeScript linting with oxlint rule-based diagnostics.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill oxlint-d0whc3r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oxlint
Source: https://github.com/d0whc3r/statsig-browser-extension/tree/main/.agents/skills/oxlint
Command: npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill oxlint-d0whc3r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you catch real JavaScript/TypeScript issues quickly and consistently without waiting on slow or noisy lint feedback loops.

Core Features & Use Cases

  • High-performance linting: Run a fast linter that’s built on the Oxc compiler stack for JS/TS projects.
  • Actionable diagnostics & safer fixes: Identify issues by rule, understand what’s wrong, and apply safe automatic fixes when appropriate.
  • Configurable quality gates: Tune rule severities, enable categories and plugins, and apply file-specific overrides for tests and scripts.

Quick Start

Run oxlint on your changed code by executing the project’s lint script (or npx oxlint) to surface and fix any rule violations immediately.

Frequently Asked Questions about oxlint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I lint JavaScript and TypeScript code fast?

To lint JavaScript and TypeScript fast, run the oxlint linter built on the Oxc compiler stack. It provides high-signal diagnostics and applies safer automatic fixes to catch real issues quickly without slow feedback loops.

How do I configure rule severities and plugins for linting?

Configure rule severities, categories, and plugins by creating a `.oxlintrc.json` or `oxlint.config.ts` file. The linter resolves this configuration to enforce specific rules and apply file-specific overrides for tests and scripts.

Can I automatically fix linting issues in my JS/TS project?

Yes, you can automatically fix linting issues in your JS/TS project. The linter identifies rule violations and applies safe automatic fixes when appropriate during your day-to-day development workflow.

What is the best way to validate code changes after edits?

The best way to validate code changes after edits is to run your project's lint script or execute `npx oxlint` directly. This surfaces and fixes any rule violations immediately by targeting the specific files you edited.

Do I need a configuration file to run oxlint?

You do not need a configuration file to run oxlint, but it is optional. Providing a resolved `.oxlintrc.json` or `oxlint.config.ts` configuration allows you to tune quality gates, enforce configured rules, and apply file overrides.