Oxlint

Detect JavaScript and TypeScript code quality issues with ESLint-compatible linting.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/nhattran998/crossfire --skill oxlint-nhattran998
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Oxlint
Source: https://github.com/nhattran998/crossfire/tree/main/.agents/skills/oxlint
Command: npx skills add https://github.com/nhattran998/crossfire --skill oxlint-nhattran998

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Oxlint helps you quickly find and prevent JavaScript/TypeScript code quality issues that would otherwise slip into your codebase, with linting that’s much faster than traditional ESLint workflows.

Core Features & Use Cases

  • Zero-Config Performance: Runs quickly across large codebases with sensible defaults.
  • ESLint-Compatible Configuration: Uses common config patterns and integrates smoothly with existing ESLint setups.
  • Rule Coverage for Web Stacks: Enforces best practices and supports JavaScript, TypeScript, and React/JSX conventions.
  • Practical Dev Workflow Support: Supports fixes, JSON reporting, ignores for generated artifacts, and CI/Editor/Pre-commit integration.

Quick Start

Install oxlint and run it against your project to automatically report lint problems, then apply fixes with oxlint --fix if needed.

Frequently Asked Questions about Oxlint

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

FAQPage Schema
How do I lint large JavaScript and TypeScript monorepos faster?▼

Run oxlint via npx or package scripts to lint large JavaScript and TypeScript monorepos faster, leveraging its high-performance static analysis to quickly identify code quality issues across extensive codebases with sensible defaults.

Can I use ESLint-compatible configuration rules with React and JSX projects?▼

Yes, you can apply ESLint-compatible configuration rules to React and JSX projects, allowing smooth integration with existing ESLint setups while enforcing web stack best practices for JavaScript and TypeScript files.

How do I integrate JavaScript and TypeScript linting into CI workflows?▼

Integrate JavaScript and TypeScript linting into CI workflows by running the linter via package scripts and utilizing its JSON reporting feature to generate CI-friendly output for automated static analysis pipelines.

Does oxlint support automatic fixes for detected code quality issues?▼

Yes, oxlint supports automatic fixes for detected code quality issues by running the command with the --fix flag, allowing developers to quickly resolve linting problems reported during static analysis.

What is the best way to ignore generated artifacts during TypeScript static analysis?▼

The best way to ignore generated artifacts during TypeScript static analysis is to use configuration overrides and ignore files, preventing unnecessary linting errors on compiled or auto-generated code in your repository.