code-quality

What it does and when to use it

Runs oxlint and oxfmt on TypeScript/JavaScript files to fix lint errors, enforce cyclomatic complexity limits, and apply consistent formatting. Use when the user asks to "lint", "format code", "run code quality checks", or mentions code quality, formatting, or static analysis.

Triggers from the description

How it works

1. When to Apply
2. Nexa Rules Gate
3. Prerequisites
4. Configuration
5. Linting
6. Formatting
7. Order
8. Verification

---
name: code-quality
description: >
  Runs oxlint and oxfmt on TypeScript/JavaScript files to fix lint errors,
  enforce cyclomatic complexity limits, and apply consistent formatting.
  Use when the user asks to "lint", "format code", "run code quality checks",
  or mentions code quality, formatting, or static analysis.
---

# Code Quality — Oxc (oxlint + oxfmt)

## When to Apply

Run these checks after generating or modifying TypeScript/JavaScript files.
This applies to implementation code, test files, and any `.ts`/`.tsx`/`.js`/`.jsx` files.
It does **not** apply to Prisma schema files.

## Nexa Rules Gate

Read and follow `${CLAUDE_PLUGIN_ROOT}/shared/readiness/NEXA_RULES_GATE.md`.

## Prerequisites

Verify `oxlint` and `oxfmt` are available in the project:

```bash
npx oxlint --version
npx oxfmt --version
```

If not installed, add them:

```bash
npm install -D oxlint oxfmt
```

## Configuration

If the project does not yet have an `oxlintrc.json` at the root, create one:

```json
{
  "rules": {
    "eslint/complexity": ["warn", { "max": 10 }]
  }
}
```

This enforces a cyclomatic complexity ceiling of 10 per function. Functions exceeding
this threshold must be refactored before the task is considered complete.

## Linting

Run oxlint with auto-fix on the source and test directories:

```bash
npx oxlint --fix --tsconfig tsconfig.json src/
```

- If there are remaining warnings or errors that cannot be auto-fixed, resolve them manually.
- **Cyclomatic complexity violations** (`eslint/complexity`): refactor the function —
  extract helpers, use early returns, or simplify conditional logic.

## Formatting

Format all changed files with oxfmt:

```bash
npx oxfmt --write src/
```

## Order

1. **Lint first** — `oxlint --fix` (fixes code issues, reports complexity violations)
2. **Format last** — `oxfmt --write` (normalizes style without changing semantics)

This order matters because the formatter may reformat the linter's fixes, but not vice versa.

## Verification

The skill is complete when:

- `npx oxlint --tsconfig tsconfig.json src/` exits with **0 errors and 0 warnings**
- `npx oxfmt --check src/` exits with code **0** (all files already formatted)
- No function exceeds cyclomatic complexity of 10

Versions

Database snapshot: 13.11.2026 · package version 1146097874e3 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100migrate-oxlint
  Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.
• 100setup-quality-ci
  Generates a GitHub Actions workflow that gates pull requests on code quality (oxlint, oxfmt) and test coverage (Vitest with v8 coverage thresholds). Use when the user asks to "set up CI for code quality", "enforce coverage in CI", "add quality gates", or mentions CI/CD for…
• 96dot-agent-oxlint
  Run the advisory Oxlint pass on JavaScript or TypeScript changes in dot-managed repositories. Use after the repository's own lint workflow whenever a task changes JS or TS files; the command checks private opt-in and local Oxlint precedence and reports only findings on changed lines.
• 100migrate-oxfmt
  Guide for migrating a project from Prettier or Biome to Oxfmt. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's formatter from Prettier or Biome to Oxfmt.
• 100sfnext-quality-gates
  Run and fix the Storefront Next quality gates before a PR or deploy: OxLint (type-aware, --max-warnings 0) plus Biome formatting, lint:a11y, lint:css, typecheck, the TypeScript-only check, bundle-size budgets, Lighthouse CI, and the pre-PR checklist. Use when pnpm lint, pnpm…
• 100oxlint
  Lint JavaScript/TypeScript at blazing speed with oxlint — a Rust-based linter 50-100x faster than ESLint. Use when someone asks to "speed up linting", "oxlint", "fast JavaScript linter", "replace ESLint", "Rust linter for JS", or "lint in CI faster". Covers rule configuration,…