# Ultracite

> Ultracite is the linter and formatter for agentic development. A zero-config preset for Oxlint, Biome, and ESLint that keeps agent-written code consistent and type-safe.

# ultracite@5.6.0
Source: https://www.ultracite.ai/changelog/ultracite-5-6-0

## Minor Changes

-   762ef70: Workflow improvements

## Patch Changes

-   f3ec41b: Backport changelog

---

# ultracite@5.6.1
Source: https://www.ultracite.ai/changelog/ultracite-5-6-1

## Patch Changes

-   44917fd: Fix package readme, move vitest to devDeps

## Minor Changes

-   762ef70: Workflow improvements

## Patch Changes

-   f3ec41b: Backport changelog

---

# ultracite@5.6.2
Source: https://www.ultracite.ai/changelog/ultracite-5-6-2

## Patch Changes

-   7b515fe: Disable useAwait rule in next config files
-   7b515fe: Improve test coverage
-   c3a9dad: Bump deps
-   3faa8c2: Add Roo Code editor rules support

---

# ultracite@5.6.3
Source: https://www.ultracite.ai/changelog/ultracite-5-6-3

## Patch Changes

-   a167b1c: Update Biome to 2.2.6

---

# ultracite@5.6.4
Source: https://www.ultracite.ai/changelog/ultracite-5-6-4

## Patch Changes

-   679719b: Temporarily disable Qwik rules

---

# ultracite@6.0.0
Source: https://www.ultracite.ai/changelog/ultracite-6-0-0

## Major Changes

-   86ee61e: Add specific Ultracite configurations

## Minor Changes

-   d704b5c: Add first-class support for Astro

## Patch Changes

-   c5c7ca1: Disable project rules
-   ff83b52: Compress Ultracite agent rules
-   8987c58: Upgrade to Biome 2.3.0
-   acd8c42: Brand and docs update
-   ed1bcb6: Docs updates and bump deps
-   d0ba90b: Tie framework selection to agent context

---

# ultracite@6.0.1
Source: https://www.ultracite.ai/changelog/ultracite-6-0-1

## Patch Changes

-   5848800: Fix legacy ultracite config

---

# ultracite@6.0.2
Source: https://www.ultracite.ai/changelog/ultracite-6-0-2

## Patch Changes

-   9566f79: Upgrade to Biome 2.3.1

---

# ultracite@6.0.3
Source: https://www.ultracite.ai/changelog/ultracite-6-0-3

## Patch Changes

-   82e5353: Drop legacy ultracite preset

---

# ultracite@6.0.4
Source: https://www.ultracite.ai/changelog/ultracite-6-0-4

## Patch Changes

-   b0a7281: setting cursor rule context to glob pattern instead of always apply

---

# ultracite@6.0.5
Source: https://www.ultracite.ai/changelog/ultracite-6-0-5

## Patch Changes

-   5f00bd3: Use overrides in presets
-   30f488e: Upgrade Biome to 2.3.2, add "noIncrementDecrement"

---

# ultracite@6.1.0
Source: https://www.ultracite.ai/changelog/ultracite-6-1-0

## Minor Changes

-   b6bdc8e: Introduce Warp agentic terminal support

## Patch Changes

-   ba72503: Fix husky initialization
-   b038a60: Fix overrides in Astro, Svelte, Vue presets having no effect
-   b7451ee: Improve core glob
-   f7ebeb8: Improve test coverage for agents

---

# ultracite@6.2.0
Source: https://www.ultracite.ai/changelog/ultracite-6-2-0

## Minor Changes

-   4035389: add cursor hooks functionality
-   18ed1f3: Refactor rules based on hooks and feedback from Cursor team

## Patch Changes

-   7aa5fd8: pass diagnostic-level filter option (stop-gap)
-   f9e2141: Update existing tsconfig files instead of creating a new root one

---

# ultracite@6.2.1
Source: https://www.ultracite.ai/changelog/ultracite-6-2-1

## Patch Changes

-   527e737: Update to Biome 2.3.3
-   d5f9d64: Disable useAwait on page.tsx and layout.tsx files in Next.js
-   eb77e3f: add allowForLoopAfterthoughts to noIncrementDecrement

---

# ultracite@6.3.0
Source: https://www.ultracite.ai/changelog/ultracite-6-3-0

## Minor Changes

-   a5a1510: Add new hooks flag, add Claude hooks support

## Patch Changes

-   0fed52b: Upgrade Biome to 2.3.4
-   a9347c8: Disable noMagicNumbers and noConsole
-   aa7f769: Updated tsconfig, package.json selector

---

# ultracite@6.3.1
Source: https://www.ultracite.ai/changelog/ultracite-6-3-1

## Patch Changes

-   908ac57: Add missing hooks cli definition

---

# ultracite@6.3.10
Source: https://www.ultracite.ai/changelog/ultracite-6-3-10

## Patch Changes

-   bc7d89f: Fix nested next.config.ts detection
-   d292922: Replace hardcoded npx commands

---

# ultracite@6.3.12
Source: https://www.ultracite.ai/changelog/ultracite-6-3-12

## Patch Changes

-   635acd1: Fix "canceled" bug for realsies this time

---

# ultracite@6.3.2
Source: https://www.ultracite.ai/changelog/ultracite-6-3-2

## Patch Changes

-   7537f01: Improve CI support

---

# ultracite@6.3.3
Source: https://www.ultracite.ai/changelog/ultracite-6-3-3

## Patch Changes

-   9132af5: Upgrade to Biome 2.3.5

---

# ultracite@6.3.4
Source: https://www.ultracite.ai/changelog/ultracite-6-3-4

## Patch Changes

-   3edc530: Bump glob to resolve dependency vulnerability
-   30ac12c: Update Biome to 2.3.6

---

# ultracite@6.3.5
Source: https://www.ultracite.ai/changelog/ultracite-6-3-5

## Patch Changes

-   1bccc30: Upgrade Biome to 2.3.7
-   3837d19: Fix Zed config
-   06a8871: Use force-ignore pattern

---

# ultracite@6.3.6
Source: https://www.ultracite.ai/changelog/ultracite-6-3-6

## Patch Changes

-   99a417c: Fix docs on quotes
-   5fb7031: Add support for max diagnostics flag
-   c66c232: Remove process.exit from CLI

---

# ultracite@6.3.7
Source: https://www.ultracite.ai/changelog/ultracite-6-3-7

## Patch Changes

-   fec49ac: added cloudflare wrangler generated file to the ignore list

---

# ultracite@6.3.8
Source: https://www.ultracite.ai/changelog/ultracite-6-3-8

## Patch Changes

-   e5e48db: Bump Biome to 2.3.8
-   0a525d9: Update docs

---

# ultracite@6.3.9
Source: https://www.ultracite.ai/changelog/ultracite-6-3-9

## Patch Changes

-   a13eb72: Add support for Factory Droid AI assistant

---

# ultracite@6.4.0
Source: https://www.ultracite.ai/changelog/ultracite-6-4-0

## Minor Changes

-   6201822: Add custom reporter

---

# ultracite@6.4.1
Source: https://www.ultracite.ai/changelog/ultracite-6-4-1

## Patch Changes

-   a8570b3: respect package manager in generated rules and commands

---

# ultracite@6.4.2
Source: https://www.ultracite.ai/changelog/ultracite-6-4-2

## Patch Changes

-   42fc700: Disable scanner rules
-   aff09df: Fix plugin install logging
-   0f57252: Upgrade to Biome 2.3.9
-   c15b770: Fix reporter
-   99dda79: Fix extension install logging
-   d759789: Bump Biome to 2.3.10

---

# ultracite@6.4.3
Source: https://www.ultracite.ai/changelog/ultracite-6-4-3

## Patch Changes

-   393a0d1: Explicitly enable css
-   127c1c6: Fix reporter bug for --unsafe flag
-   41a73ba: Fix file-based metadata
-   43b07be: Fix tsconfig patching
-   9d1d374: Add support for pre-commit (python)
-   f9256db: Add support for Antigravity

---

# ultracite@6.5.0
Source: https://www.ultracite.ai/changelog/ultracite-6-5-0

## Minor Changes

-   628a5c3: Disable nursery rules

## Patch Changes

-   a942392: Use `interface` as consistent type definition

---

# ultracite@7.0.0
Source: https://www.ultracite.ai/changelog/ultracite-7-0-0

## Major Changes

-   c4a205f: Remove i18n docs
-   c4a205f: Remove custom reporter
-   c4a205f: Scaffold support for ESLint and Oxlint
-   c4a205f: Add support for Amazon Q, Crush, Firebender, OpenCode, Qwen and Trae
-   c4a205f: Move biome config under `biome`

## Patch Changes

-   5538022: Increase max allowed complexity
-   5508d47: Remove GraphQL override that disables formatter/linter
-   e1b6be6: Fix undefined input to fix command
-   618ae17: Fix changesets
-   Updated dependencies [c4a205f]
    -   @repo/data@2.0.0

---

# ultracite@7.0.1
Source: https://www.ultracite.ai/changelog/ultracite-7-0-1

## Patch Changes

-   a8408b6: Fix bundling issues

---

# ultracite@7.0.10
Source: https://www.ultracite.ai/changelog/ultracite-7-0-10

## Patch Changes

-   a7b34ed: Add Vercel Agent support
-   b6658ce: Add Claude Code hook integration to run `ultracite fix` after `Write`/`Edit` tool usage.

---

# ultracite@7.0.11
Source: https://www.ultracite.ai/changelog/ultracite-7-0-11

## Patch Changes

-   79d2756: fix: exit with code 1 when check/fix finds errors
-   c032612: Fix: Parser Errors on .jsonc Files Due to Comments
-   a556651: Move oxlint to optionalDependencies or peerDependencies

---

# ultracite@7.0.12
Source: https://www.ultracite.ai/changelog/ultracite-7-0-12

## Patch Changes

-   f328fc6: Update nypm to remove dependency on corepack
-   6f638fa: Fix error message when exiting with code 1
-   f328fc6: Fix eslint dependencies during initialization
-   f328fc6: Allow comments in json files

---

# ultracite@7.0.2
Source: https://www.ultracite.ai/changelog/ultracite-7-0-2

## Patch Changes

-   246c1fc: Update docs and README
    Remove catalog dependencies

---

# ultracite@7.0.3
Source: https://www.ultracite.ai/changelog/ultracite-7-0-3

## Patch Changes

-   92eaa89: Cleanup dist files

---

# ultracite@7.0.4
Source: https://www.ultracite.ai/changelog/ultracite-7-0-4

## Patch Changes

-   7e9b76c: Fix legacy imports

---

# ultracite@7.0.5
Source: https://www.ultracite.ai/changelog/ultracite-7-0-5

## Patch Changes

-   ab47642: add --type-aware and --type-check flags for oxlint

---

# ultracite@7.0.6
Source: https://www.ultracite.ai/changelog/ultracite-7-0-6

## Patch Changes

-   702f6b5: Upgrade Biome to 2.3.11

---

# ultracite@7.0.7
Source: https://www.ultracite.ai/changelog/ultracite-7-0-7

## Patch Changes

-   ea7a6dc: Fix oxlint import path
-   a6e43a0: Add more CLI options for oxlint, oxfmt and biome
-   ad52a16: Fix linter provider mention in agent rules

---

# ultracite@7.0.8
Source: https://www.ultracite.ai/changelog/ultracite-7-0-8

## Patch Changes

-   a9efe80: Add Cursor CLI as agent
-   00fb477: Add support for Mistral Vibe

---

# ultracite@7.0.9
Source: https://www.ultracite.ai/changelog/ultracite-7-0-9

## Patch Changes

-   95dd898: Disable sort-imports in favor of oxfmt
-   c72d2b3: Disable react/jsx-max-depth
-   2ae8976: Disable typescript/require-await

---

# ultracite@7.1.1
Source: https://www.ultracite.ai/changelog/ultracite-7-1-1

## Patch Changes

-   0e9af01: Automatically add scripts to root package.json
-   656f6d7: fix(oxlint-remix): ignore unicorn rules for generated routeTree.gen.ts

---

# ultracite@7.1.2
Source: https://www.ultracite.ai/changelog/ultracite-7-1-2

## Patch Changes

-   9d443b6: Fix func-style config in oxlint
-   3d9b488: Fix: argument --unsafe cannot be used multiple times in this context
-   f06808f: Don't pass options to formatters, only linters

---

# ultracite@7.1.3
Source: https://www.ultracite.ai/changelog/ultracite-7-1-3

## Patch Changes

-   c60533d: Fix oxlint import/consistent-type-specifier-style

---

# ultracite@7.1.4
Source: https://www.ultracite.ai/changelog/ultracite-7-1-4

## Patch Changes

-   34c79bb: Fix conflicting oxlint rules

---

# ultracite@7.1.5
Source: https://www.ultracite.ai/changelog/ultracite-7-1-5

## Patch Changes

-   c8fdacf: fix: detectLinter() doesn't walk up directory tree, Breaks monorepo subdirectory usage
-   c79c3b0: Fix lefthook file configuration
-   4b9d206: Make useBlockStatements fix safe
-   8e9e728: Add support for NestJS
-   d0ae8f3: Fix: Biome removes all imports in Svelte files on save instead of organizing them

---

# ultracite@7.10.0
Source: https://www.ultracite.ai/changelog/ultracite-7-10-0

## Minor Changes

- cd0a36c: Add `--claude` and `--codex` flags to `ultracite fix`. After the normal autofix pass, remaining diagnostics are handed to the Claude Code or Codex CLI non-interactively, one agent run per affected file, with a live per-issue spinner that flips to ✓/✗ once the fix is verified by a re-lint. Fixes that don't survive verification are retried (up to 3 attempts per file) with the fresh diagnostics and feedback that the previous approach failed. Works with all three linter modes (Oxlint, Biome, ESLint); exits non-zero if any issues remain, matching the plain `fix` contract.
- e089510: Scope React Doctor's framework-specific rules to per-framework add-on presets (#752)

  The `ultracite/oxlint/js-plugins` preset no longer enables React Doctor's `nextjs-*` and TanStack (`query-*`, `tanstack-start-*`) rules for every consumer. Rules like `nextjs-no-img-element` and `tanstack-start-no-anchor-element` fire on plain `<img>`/`<a>` JSX and recommend framework replacements, which falsely errored in Vite + React and other non-Next/non-TanStack projects.

  Those rules now live in two new add-on presets:

  - `ultracite/oxlint/next/js-plugins`
  - `ultracite/oxlint/tanstack/js-plugins`

  `ultracite init` wires the matching add-on automatically when you select the framework together with `oxlint-plugin-react-doctor`. If you manage `oxlint.config.ts` by hand and use Next.js or TanStack, add the matching add-on preset to `extends` alongside `js-plugins` to keep those rules — or re-run `npx ultracite init`.

  Also fixes re-running `init` on a config that already extends `js-plugins` producing a duplicate `import jsPlugins` declaration.

## Patch Changes

- 3320cd8: Update Biome to 2.5.6. No stable (non-nursery) rules were added, removed, or promoted between 2.5.3 and 2.5.6, so the preset configs are unchanged.
- 477cd6e: Update ESLint to 10.8.0 and all ESLint plugins to their latest versions. Highlights:

  - `eslint-plugin-react-doctor` 0.9.3: the react preset expands from 149 to 417 rules, adopting the upstream `recommended` set (react-router, three.js/r3f, ink, motion, remotion, zustand/valtio/mobx, and more) while excluding rules that duplicate already-enabled `react`, `react-hooks`, and `jsx-a11y` rules. The next preset gains `nextjs-async-dynamic-api-not-awaited` and `nextjs-metadata-url-consistency`; the tanstack preset gains `tanstack-start-missing-scripts`, `query-floating-mutate-async`, and `query-no-mutation-in-effect-as-read`.
  - `eslint-plugin-unicorn` 72: adds `no-missing-local-resource`, `no-multiple-promise-resolver-calls`, `no-shorthand-property-overrides`, `no-transition-all`, `no-unnecessary-string-trim`, `no-useless-re-export`, `prefer-then-catch`, and `require-frontmatter-fields`. CSS-only rules are excluded from the preset since they fail config validation for JS files.
  - `eslint-plugin-sonarjs` 4.2: adds 11 rules including `no-fixed-wait-in-tests`, `parameterized-tests`, `assertions-in-test-cases`, `prefer-native-lodash-alternative`, and `explicit-test-skip`.
  - `typescript-eslint` 8.65: `@typescript-eslint/no-loop-func` and `@typescript-eslint/no-restricted-imports` were deprecated upstream in favor of the base rules, which now apply to TypeScript files.
  - `eslint-plugin-astro` 3: removes `astro/no-omitted-end-tags` and `astro/valid-compile`.
  - `eslint-plugin-svelte` 3.22: adds `no-bind-value-on-checkable-inputs` and `no-conflicting-module-names`; `no-restricted-html-elements` is now off because its schema requires a user-supplied element list.
  - `@angular-eslint/eslint-plugin` 22.1: adds `inject-at-top` and `prefer-service-decorator`.

- b81578b: Fix the useSortedPackageJson action not being executed by turning on assist actions for package.json-like files.
- 9ec454a: Update oxlint to 1.76.0 and oxfmt to 0.61.0. New stable rules added to the presets: `oxc/bad-match-all-arg`, `id-denylist`, `node/exports-style` (core), `react/function-component-definition` with arrow-function components (react), and `vitest/padding-around-test-blocks` (vitest). `node/no-top-level-await` is off — top-level await is idiomatic in ESM, Astro frontmatter, and build scripts — and the ESLint preset's `n/no-top-level-await` is now off to match. No rules were removed or promoted out of nursery.
- ba61c02: Fix generated oxlint.config.ts accessing plugin.name on ExternalPluginEntry without narrowing the string form, which caused a TypeScript error in projects that type-check the config (#753)

---

# ultracite@7.10.1
Source: https://www.ultracite.ai/changelog/ultracite-7-10-1

## Patch Changes

- d018b7f: Fix several agent fix mode (`fix --claude`/`--codex`) issues: runs no longer abort with ENOBUFS when linter JSON output exceeds 1MB, user-supplied format/reporter flags can no longer override the JSON reporter and break parsing, a stuck agent process is force-killed 10 seconds after the timeout instead of hanging forever, and the progress renderer no longer garbles TTY output when file paths and rule names exceed the terminal width.
- d018b7f: Fix Biome config migration leaving the legacy bare `"extends": ["ultracite"]` form in place, which breaks Biome's module resolution since the package has no root export. It's now mapped to `ultracite/biome/core`.
- d018b7f: Fix `ultracite doctor` reporting spurious failures: config checks now walk up parent directories (matching `check`/`fix` and the linters themselves) so monorepo packages inheriting a root config pass, `.oxlintrc.json` is accepted as a valid oxlint config (with a migration suggestion), and Prettier/Stylelint configs declared via `package.json` keys are recognized.
- d018b7f: Fix `ultracite init` corrupting existing Prettier/Stylelint/ESLint configs by writing an ESM module into JSON/YAML/TOML/CJS config files (e.g. `.prettierrc`, `eslint.config.cjs`). Updates now write the default `.mjs` config instead and remove the incompatible file so it can't shadow the new one.
- d018b7f: Fix `ultracite check`/`fix` misrouting space-separated flag values (e.g. `--max-warnings 10`) into the file list, which scrambled the underlying linter invocation and made formatters fail on bogus targets. Positional files listed before a `--` separator are also kept as lint targets instead of being reclassified as passthrough, which could silently widen formatter runs to the whole project.
- d018b7f: Fix Lefthook and pre-commit YAML updates silently doing nothing on common config shapes: the Lefthook job is now inserted correctly when `jobs:` isn't the first key under `pre-commit:` (and no longer matches a `jobs:` key in a different hook), `repos: []` in `.pre-commit-config.yaml` is handled, and shapes that can't be safely edited produce a warning instead of writing the file back unchanged.
- d018b7f: Fix the Husky integration overwriting an existing `.husky/pre-commit` hook: `ultracite init` ran `husky init`, which unconditionally replaces the hook with `npm test`. It now runs plain `husky` to set up the hooks infrastructure without touching the hook file.
- d018b7f: Fix `ultracite init` destroying user files it couldn't parse or merge: unparseable `tsconfig.json` files are no longer replaced with a minimal config, unparseable `.vscode`/`.zed` settings are no longer overwritten wholesale, and lint-staged configs with function-valued entries are left untouched — all now warn and skip instead.
- d018b7f: Fix re-running `ultracite init` on an oxlint setup silently enabling the full js-plugins preset — the previously selected JS plugins are now preserved when no new selection is made. Init also no longer flips an explicit `"type": "commonjs"` in package.json to `"module"`; it warns instead.
- d018b7f: Fix switching linters removing `storybook` from the project's dependencies. It was swept into the removal set as a peer of `eslint-plugin-storybook`, but it's a user-facing tool a project may use independently of linting.
- d018b7f: Fix Stylelint target generation dropping directories with a dot in their name (e.g. `app.web`) and producing non-matching globs from Windows-style backslash paths. Framework detection also handles negated workspace patterns (`!packages/legacy`) again.
- d018b7f: Fix the CLI becoming a silent no-op (exiting 0 without linting anything) when a generic `TEST` environment variable is set, as is common in CI matrices. The internal test guard now uses `ULTRACITE_TEST`.
- 36c7b80: Move @typescript-eslint/utils from dependencies to devDependencies. It was accidentally shipped as a runtime dependency in 7.9.0, pulling eslint and the typescript-eslint packages into every consumer's install (including oxlint-only setups) via npm's automatic peer dependency installation. Nothing in the published package imports it — it only exists to support the workspace-internal rule-parity script.

---

# ultracite@7.10.2
Source: https://www.ultracite.ai/changelog/ultracite-7-10-2

## Patch Changes

- 1c48c68: Enable Tailwind CSS class sorting (`sortTailwindcss`) in the Oxfmt preset. Classes in `class`/`className` attributes and in `clsx`, `cva`, `tw`, `twMerge`, `cn`, `twJoin`, and `tv` calls are now sorted using the same algorithm as `prettier-plugin-tailwindcss`, matching the behavior of the Prettier preset (which always loads the Tailwind plugin) and the Biome preset's `useSortedClasses` rule. Projects without Tailwind installed are unaffected beyond class strings being sorted against the default theme, and oxfmt versions older than 0.35.0 ignore the option.
- dc78be4: Stop sorting TanStack route option keys in route files. TanStack Router's route option types are order-sensitive (`head`/`component` infer `loaderData` from properties declared before them), so the Biome `useSortedKeys` source action rewrote `createFileRoute` literals into an order that breaks type inference (`loaderData` becomes `never`). The Biome TanStack preset now disables `useSortedKeys` for route files, and the oxlint TanStack preset disables `sort-keys` there so route files aren't caught between it and `react-doctor/tanstack-start-route-property-order`.

---

# ultracite@7.10.3
Source: https://www.ultracite.ai/changelog/ultracite-7-10-3

## Patch Changes

- a1fa9c4: Replace the hand-rolled package `exports` map matching in the config-resolution doctor check with the resolve.exports library, which implements Node's full `PACKAGE_TARGET_RESOLVE` algorithm (wildcard patterns, key-order precedence, conditional exports, and array fallbacks). The manual `node_modules` walk is kept intentionally — it exists to avoid Bun's auto-install cache resolving specifiers the project's own `node_modules` can't.
- 414ea80: Replace the hand-rolled monorepo workspace scan in framework detection with the find-workspaces library. Workspace declarations from package.json (array and yarn-classic object form) and pnpm-workspace.yaml — including negated globs — are now resolved by the library instead of manual pattern collection and globbing, and lerna/bolt monorepos are picked up as well.
- a9a1989: Replace the hand-rolled upward directory walks in `findNearestFile` and `detectLinter` with the empathic library's `find.any`, which checks candidate names in order within each directory before moving to the parent — the same per-directory precedence the previous implementation enforced manually.
- 27b2707: Use magicast to update ESM lint-staged config files during `ultracite init`. The config is now edited as an AST instead of being imported and re-serialized, so comments and function-valued entries elsewhere in the config survive the update, and the user's config code is no longer executed. If the Ultracite glob pattern is already owned by a non-array value, or the config isn't a mergeable object literal (e.g. `defineConfig(...)`), init warns and leaves the file untouched instead of rewriting it. CommonJS configs keep the previous behavior.
- f2529b8: Rewrite the agent-fix progress renderer on top of log-update, cli-truncate, and string-width. log-update now owns the in-place block rewriting that was previously done with manual cursor-up/clear-line escape sequences, and line truncation is measured by display width instead of code units — so lint messages containing emoji or CJK text can no longer overflow the terminal row and corrupt the animated block.
- 277b9d6: Replace the hand-rolled child-process handling in the agent fix runner with execa. The timeout → SIGTERM → grace period → SIGKILL escalation, stderr capture, and spawn-failure handling now use execa's `timeout` and `forceKillAfterDelay` options, which are battle-tested across platforms (including Windows kill semantics the manual implementation didn't cover). Behavior is unchanged: agent runs still time out after 5 minutes, escalate to SIGKILL after a 10-second grace period, and report a capped stderr tail.
- 1614a80: Drop the direct cross-spawn dependency: all synchronous process spawning (linter runs, tool version checks, editor extension installs, skill installs) now goes through a small adapter over execa's sync API, which owns the Windows spawn semantics cross-spawn provided. The adapter preserves the spawnSync result shape (`status`/`signal`/`error`/`stdout`), always disables shell interpretation, and always decodes output as UTF-8. execa was already a dependency for the agent fix runner, so this consolidates on one process-spawning library.
- ac114b4: Replace the glob dependency with fast-glob for the tsconfig.json scan during init. fast-glob was already in the dependency tree via find-workspaces, so this drops glob's transitive dependencies (minipass, path-scurry, etc.) from the install without changing behavior.

---

# ultracite@7.10.4
Source: https://www.ultracite.ai/changelog/ultracite-7-10-4

## Patch Changes

- 417a85a: Add an opt-in `ultracite/oxlint/anti-slop` preset that ships a vendored, self-contained build of the [anti-slop](https://github.com/dmmulroy/anti-slop) Oxlint plugin — fifteen rules that reject low-evidence TypeScript and JavaScript patterns (unjustified type assertions, `unknown` leaking through signatures, `Reflect`-based access, module mocking, and more). Extend it alongside `ultracite/oxlint/core`; nothing extra to install. The preset also turns off two core rules that conflict with anti-slop's widening checks (`typescript/consistent-indexed-object-style` and `unicorn/no-immediate-mutation`) when extended after core.
- 4d3fab8: Move `suspicious/useArraySortCompare` from the Biome core config to the opt-in type-aware config. The rule is in Biome's `types` domain — it type-infers the receiver of every method call before checking the method name, which made `ultracite check` up to ~260x slower on projects with expensive library types (zod, better-auth, Prisma). It now only runs when type-aware linting is explicitly enabled, alongside the other type/project-domain rules. Fixes #768.

---

# ultracite@7.10.5
Source: https://www.ultracite.ai/changelog/ultracite-7-10-5

## Patch Changes

- 8df6ad0: Offer the vendored `anti-slop` Oxlint preset during `ultracite init` — it now appears in the JS-plugins prompt when you pick Oxlint, and non-interactive setup accepts it via `--js-plugins anti-slop`. Selecting it adds `ultracite/oxlint/anti-slop` to the generated config's `extends`; since the preset is vendored inside Ultracite, nothing extra is installed.
- cd229e9: Bump the `oxlint-plugin-react-doctor` pin from `^0.7.1` to `^0.9.12`, so `ultracite init` installs the current plugin. All react-doctor rules enabled by the js-plugins presets still exist in 0.9.12, and the ported rules run in curated mode via the settings shipped alongside this release (#771).
- e1ac886: Pin React Doctor's ported rules to their framework-aware "curated" mode (#771). react-doctor 0.9.x rewrote its ported oxc/react-refresh rules — notably `only-export-components` — with a stripped-down default mode: no framework detection, no route-file skipping, and `allowConstantExport` off, so Next.js route-segment exports like `export const dynamic = "force-static"` or `metadata` were flagged as non-component exports in every route file. The ESLint react preset now sets `settings["react-doctor"].portedRuleMode: "curated"`, and generated oxlint configs apply a new `jsPluginSettings` export from `ultracite/oxlint/js-plugins` on the root config (oxlint does not merge `settings` from extended configs, so the setting cannot ride along inside the preset). If you extend the js-plugins preset manually, add `settings: jsPluginSettings` to your root oxlint config.
- c27fe36: Generate oxlint configs that enable a subset of the JS plugins via a new `selectJsPlugins` export from `ultracite/oxlint/js-plugins`, instead of inlining the filtering logic into the generated file. The inlined block contained a `typeof` check that user-side lint presets flagged (`anti-slop/no-runtime-typeof`, #770); the generated config is now a one-line extend, is emitted already formatted (including the previously missing blank line after imports), and re-running `ultracite init` migrates existing configs with the old inlined block automatically.
- 0616523: Update the vendored `anti-slop` Oxlint plugin to upstream commit `446268e`, picking up fixes to `no-object-parameters` and `no-unknown-returns` (respect lexical type binders in alias resolution) and a new `allowInTypeGuards` option on `no-runtime-typeof`. The `ultracite/oxlint/anti-slop` preset enables `allowInTypeGuards`, so `typeof` checks inside type predicate functions (`(x): x is T`) no longer need disable comments — predicates are the named-boundary pattern the rule pushes toward (dmmulroy/anti-slop#10).

---

# ultracite@7.10.6
Source: https://www.ultracite.ai/changelog/ultracite-7-10-6

## Patch Changes

- 972b946: Update the oxlint presets for oxlint 1.79: replace the removed `react/react-compiler` rule with the 22 new React Compiler rules in the react preset, add `jsdoc/no-blank-blocks` and `one-var` to the core preset (mirrored in the ESLint presets), and require oxlint ^1.79.0
- 2d5bbdb: Declare the `jsPluginSettings` named export in the `ultracite/oxlint/js-plugins` type declarations, so the documented (and `ultracite init`-generated) `import jsPlugins, { jsPluginSettings } from "ultracite/oxlint/js-plugins"` type-checks (#773)
- 56aef65: Refresh the toolchain versions that `ultracite init` installs into projects: `@biomejs/biome` 2.5.9, the ESLint plugin family (including eslint-plugin-cypress 7, eslint-plugin-jsdoc 64, eslint-plugin-solid 0.15, and eslint-plugin-unicorn 73 — the dynamic presets adopt their new rules automatically), and `prettier-plugin-svelte` 4.1.1 / `prettier-plugin-tailwindcss` 0.8.1

---

# ultracite@7.10.7
Source: https://www.ultracite.ai/changelog/ultracite-7-10-7

## Patch Changes

- 15f7ae0: Add support for the Aube package manager: `ultracite init --pm aube` is now accepted and projects with an `aube-lock.yaml` lockfile are detected automatically
- 1afc8fe: Re-declare selected Oxlint JS plugins on the root config so dependency analyzers see them. `ultracite init --linter oxlint --js-plugins ...` now generates `const jsPlugins = selectJsPlugins([...])` and adds `jsPlugins: jsPlugins.jsPlugins` to the root config (also when the full `ultracite/oxlint/js-plugins` preset is extended). Knip only resolves `jsPlugins` from the root Oxlint config and never walks `extends`, so `eslint-plugin-github`, `eslint-plugin-sonarjs`, and `oxlint-plugin-react-doctor` were reported as unused devDependencies. Oxlint dedupes the plugin between the root and the extended preset, so linting is unchanged.

  Also fix `ultracite update` dropping the `js-plugins` preset from `extends` when the config used the documented `import jsPlugins, { jsPluginSettings } from "ultracite/oxlint/js-plugins"` form: the import parser only matched bare default imports. The regenerated full-preset config keeps `settings: jsPluginSettings` on the root as well.

- 20b06bf: Ignore `.alchemy` across all linters and formatters. Alchemy (alchemy.run) writes local state and generated bindings to a `.alchemy` directory. It is now part of the shared ignore patterns synced into Biome's `files.includes` and imported by oxlint, oxfmt, and ESLint, and the Stylelint preset ignores it via `ignoreFiles`. Prettier needs no change: it already respects `.gitignore`/`.prettierignore`.
- 6e9286c: Run `lefthook install` during `ultracite init` through the same spawn adapter as every other tool invocation instead of `execSync`, so it no longer goes through a shell and gets the same Windows command resolution as `husky`, the linters, and editor extension installs.
- 8b24f34: Add support for the Nub package manager: `ultracite init --pm nub` is now accepted and projects with a `nub.lock` lockfile are detected automatically (requires nypm ^0.6.9)
- 240cb6b: Install into the workspace root correctly for Nub and Aube monorepos: nypm emits no root selector for them, so `nub add` ran without `-w` and was refused. Ultracite now hands nypm pnpm's flag set for these pnpm-compatible CLIs, producing `nub add --workspace-root --save-dev ultracite`
- 44ecbba: Add Vitest type-test files (`**/*.{test-d,spec-d}.{ts,tsx,js,jsx}`) to the test-file globs so the shared test relaxations and the Vitest rule overrides apply to them, and enable the Vitest plugin's `typecheck` setting in the ESLint preset so `expectTypeOf`/`assertType` count as assertions.
- 7ba6bb8: Package the reusable Ultracite agent skill with the npm distribution.

---

# ultracite@7.10.8
Source: https://www.ultracite.ai/changelog/ultracite-7-10-8

## Patch Changes

- 2a43fdd: Turn off `unicorn/prefer-reflect-apply` in the `ultracite/oxlint/anti-slop` preset. When extended after `ultracite/oxlint/core`, the core rule recommended rewriting `Function#apply()` to `Reflect.apply()`, which anti-slop's `no-reflect-apply` then rejected, leaving no way to satisfy both. Direct-call guidance for `.apply()` still comes from `eslint/prefer-spread` and `eslint/no-useless-call`.
- 03196df: Update `@biomejs/biome` to 2.5.12. Releases 2.5.10 through 2.5.12 only add nursery rules, which the Biome presets exclude, so the presets are unchanged. The releases also carry linter and formatter fixes, including fewer `noUnusedVariables` false positives on merged interfaces, namespaces, and overload type parameters, an unsafe-by-default fix for `noThisInStatic`, and a large batch of Astro expression parsing fixes.
- 031b867: Update oxfmt to 0.66.0. The 0.65 and 0.66 releases are formatter fixes only, mainly around comment placement between a statement head and its body, suppressed statements (decorators, typecast parens, semicolons), custom side-effect groups in `sortImports`, CommonMark list interruption in JSDoc, and trailing whitespace in YAML block scalars. The `:::` container-directive fence patch is re-targeted to the new markdown bundle; the patched code itself is unchanged.
- 54affee: Update oxlint to 1.81.0. The 1.80 and 1.81 releases add no rules and remove none, so the presets are unchanged and the peer range stays at ^1.79.0. Notable fixes carried in: `no-use-before-define` now runs on JS and JSX files, `object-shorthand` preserves `__proto__` semantics, `unicorn/prefer-math-min-max` no longer applies an unsafe autofix, and JS plugin diagnostics with invalid or reversed locations are clamped instead of crashing.
- 0b058d1: Fix `ultracite fix --codex` failing on recent Codex CLI releases. The Codex adapter invoked `codex exec --full-auto`, a flag Codex has since removed, so every attempt failed at argument parsing. It now runs `codex exec --sandbox workspace-write`, the equivalent non-interactive, workspace-scoped mode, which is also accepted by older Codex versions. Resolves #794.
- e2346bb: Update the ESLint family to latest: eslint 10.9.1, typescript-eslint 8.69.0, eslint-plugin-unicorn 74, eslint-plugin-solid 0.17, eslint-plugin-jsdoc 64.3.5, eslint-plugin-react-doctor and oxlint-plugin-react-doctor 0.9.13, globals 17.12, and the angular, nestjs-typed, next, tanstack-query, cypress, html, jest and storybook plugins. The dynamic presets pick up the new rules automatically: the solid preset gains the eleven rules added in eslint-plugin-solid 0.16 and 0.17 (`removed-api`, `no-single-arg-create-effect`, `no-accessor-as-prop`, `valid-use-server`, `require-async-server-function`, `no-invalid-server-capture`, `no-browser-globals-in-server-function`, `no-module-scope-reactive-primitive`, `no-restated-default-options`, `prefer-onSettled-for-side-effects`, `prefer-structured-class`), which only report Solid 2.0 issues when `settings.solid.version` is set to 2 and stay silent on Solid 1.x code; the nestjs preset gains `forward-ref-injection-should-use-wrapper-type`, `swagger-file-upload-should-be-documented` and `uploaded-file-should-be-validated`. The curated jsdoc and react-doctor lists are unchanged. No enabled rule was removed or deprecated, and the ESLint/oxlint parity check still passes.
- 7b0456e: `ultracite fix` now runs lint fixes before the formatter: oxlint before oxfmt, and ESLint then Stylelint before Prettier. A fixer can insert unformatted code, such as the braces `curly` adds, the imports `consistent-type-specifier-style` splits, or the font names Stylelint requotes, and running the formatter first left that code unformatted until the next run. Fixer-inserted code is now formatted in the same run. The `--claude` and `--codex` agent passes follow the same order.
  
  `unicorn/no-nested-ternary` is now off in the oxlint and ESLint presets: its fixer adds parentheses that oxfmt and Prettier remove, so the two tools rewrote the file on every run. The core `no-nested-ternary` rule still reports nested ternaries.
- 8ddc078: Enable three rules added in Stylelint 17 in the Stylelint preset: `selector-no-deprecated` and `selector-no-invalid` report selectors that CSS has dropped or that cannot parse, and `relative-selector-nesting-notation` is set to `explicit`, so nested relative selectors are written `& > b` rather than `> b`. The `property-layout-mappings`, `unit-layout-mappings` and `value-keyword-layout-mappings` rules are deliberately left off, since they reject every physical property, unit and keyword and can only autofix with a per-project `languageOptions.directionality` setting. The repo's own Stylelint lock is refreshed from 16.26.1 to 17.14.1, which the config packages already required; `ultracite init` already installs `stylelint@latest` so users are unaffected by the lock change.
- 4609d79: Update the vendored `anti-slop` Oxlint plugin to upstream v0.1.2 (commit `e8c4880`). The rule set is unchanged; this picks up a round of correctness fixes: `no-known-value-widening` now also reports known values passed into local `unknown`-typed type predicates, `no-object-parameters`, `no-unknown-parameters`, `no-unknown-returns` and `no-unknown-type-aliases` resolve scoped and transparent generic aliases (including block-scoped aliases and forward references), `no-unknown-returns` covers `PromiseLike<unknown>`, `no-unsafe-dictionary-type` allows generic constraints such as `T extends Record<string, unknown>`, `no-runtime-typeof` always allows existence probes against `"undefined"`, `no-shape-in-symbol-names` allows static member reads such as Zod's `schema.shape`, and `require-safety-comment-for-type-assertion` rejects empty justifications and gains a `markers` option (default `["SAFETY"]`). Upstream also added a separate opt-in `anti-slop-effect` plugin for Effect projects, which is not vendored.

---

# ultracite@7.11.0
Source: https://www.ultracite.ai/changelog/ultracite-7-11-0

## Minor Changes

- d5d241f: Add `ultracite upgrade`, and make version drift between Ultracite and its linter visible instead of a crash. Bumping `ultracite` without bumping the linter fails on the next `check`/`fix` with Biome's `Found an unknown key` error (and the equivalent for ESLint and Oxlint), because each release enables rules from a specific linter version.
  
  - `ultracite upgrade` installs the latest `ultracite`, prints a release-notes link for the versions you crossed, then hands off to the freshly installed CLI to reinstall your toolchain at the versions that release was verified with: Biome; ESLint, Prettier, Stylelint and the plugins the preset imports; or Oxlint and Oxfmt. Optional extras already in your `package.json` (framework plugins, Oxlint JS plugins, `oxlint-tsgolint`) are bumped as well. Config files are never rewritten, and the run ends with the same diagnostics as `doctor`.
  - `ultracite doctor` now checks the installed Biome, ESLint, Prettier, Stylelint, Oxlint and Oxfmt versions against the range this release supports. Too old fails the check and points at `ultracite upgrade`; newer than the verified range only warns.
  - The supported ranges are declared as optional peer dependencies so package managers warn when they drift: `@biomejs/biome ^2.5.0`, `eslint ^10.0.0`, `prettier ^3.0.0`, `stylelint ^17.0.0`, `oxlint ^1.79.0`, `oxfmt >=0.40.0`. `ultracite init` now installs Prettier and Stylelint from those ranges instead of `latest`.
  
  Requires Biome >= 2.5.0, ESLint >= 10.0.0, Prettier >= 3.0.0, Stylelint >= 17.0.0, Oxlint >= 1.79.0 and Oxfmt >= 0.40.0.

## Patch Changes

- 27d06f2: Update dependencies (`@clack/prompts`, `semver`, `zod`, ESLint plugins).
- d322691: Default `ultracite init` to Oxlint + Oxfmt when `--linter` is omitted in quiet or non-interactive mode
- c677cf5: Recommend Oxlint + Oxfmt in the `ultracite init` linter prompt and list it first
- c5be848: Disable `no-use-before-define` in TanStack Router route files for the oxlint tanstack preset. File routes are mutually recursive (`Route` references the component, and the component calls `Route.useParams()`), so no declaration order could satisfy the rule.

---

# ultracite@7.11.1
Source: https://www.ultracite.ai/changelog/ultracite-7-11-1

## Patch Changes

- 24b2797: Update oxfmt to 0.67.0 and re-target the markdown `:::` fence patch to the new dist chunk. The release changes no options; it fixes CSS/SCSS/Less comment preservation and a few JSDoc-cast edge cases in member chains.
- 24b2797: Update oxlint to 1.82.0. The release adds and removes no rules, so the presets are unchanged apart from one new option: `no-unmodified-loop-condition` now runs with `checkConditionalExpressions: true` in the oxlint and ESLint core presets, so each branch of a ternary in a loop condition must be modified inside the loop rather than only the expression as a whole.
- 24b2797: Update the ESLint family: `@angular-eslint/eslint-plugin` 22.5, `@typescript-eslint/*` 8.70, `eslint-plugin-solid` 0.18, `eslint-plugin-vue` 10.11, `eslint-plugin-jsdoc` 64.3.8, `eslint-plugin-cypress` 7.0.2, `@darraghor/eslint-plugin-nestjs-typed` 7.5.2 and `prettier-plugin-astro` 1.0. The dynamic presets pick up the seven new rules automatically: `@typescript-eslint/no-generated-empty-object-type`, `@angular-eslint/reactive-context-must-read-signal`, `vue/no-shadow-native-events`, and Solid's `no-boolean-enumerated-attribute`, `no-store-mutation-outside-setter`, `no-unused-signal` and `no-write-in-pure-computation`. Note that `prettier-plugin-astro` 1.0 is a rewrite on the Astro 7 Rust compiler (Node 22.12+); expect whitespace diffs on first run and mirror any custom `compressHTML` via its new `astroCompressHTML` option.
- 24b2797: Refresh the stylelint lock to 17.15.0 and enable its new `selector-no-unmatchable` rule, which flags selectors that can never match (for example `label:checked`, `::before:first-child` or `:is(::before)`).
- a71dda4: Stop sorting object keys across the whole TanStack presets, not just route files. TanStack Query mutation options are order-sensitive too: TypeScript infers the `onMutate` context from context-sensitive callbacks in source order, so moving `onError`/`onSettled` above `onMutate` turns the context into `{}` and `ultracite fix` broke type-correct code (`TS2339: Property '...' does not exist on type '{}'`). Mutation and query options live anywhere (hooks, components, colocated files), so the route-file exemption could not cover them. `ultracite/oxlint/tanstack` now sets `sort-keys` to `off` and `ultracite/biome/tanstack` now sets `useSortedKeys` to `off` for all files.
- a9db61c: Disable `github/filenames-match-regex` for file-based route directories (`**/routes/**`) in the oxlint js-plugins preset, matching the existing `unicorn/filename-case` exemption in the TanStack preset. TanStack Router filenames such as `__root.tsx`, `$.tsx`, and `posts.$postId.tsx` no longer fail the GitHub filename rule. Resolves #799.

---

# ultracite@7.12.0
Source: https://www.ultracite.ai/changelog/ultracite-7-12-0

## Minor Changes

- 1f427d7: Add an opt-in `ultracite/oxlint/shadcn` preset for [`@shadcn/lint`](https://github.com/shadcn-ui/lint), shadcn's agent-first linter for Tailwind v4 design systems. All six rules (`no-restyle`, `no-raw-colors`, `no-arbitrary-values`, `no-inline-styles`, `no-unknown-classes`, `require-static-classes`) run at `error` with the upstream `allow: ["layout"]` policy, and the component-authoring rules are relaxed inside `**/components/ui/**`. Enable it with `ultracite init --linter oxlint --js-plugins @shadcn/lint`, or extend it alongside `ultracite/oxlint/core` after installing `@shadcn/lint`.

## Patch Changes

- 600e991: Accept file-based page route filenames in `github/filenames-match-regex`. Files under `pages/` (Astro, Next.js pages router) now match a bracket-aware pattern, so dynamic, rest and optional parameters such as `[slug].astro`, `[...slug].ts` and `[[...slug]].tsx` pass while non-route names like `BadPage.ts` are still rejected.
- 66f97bb: Allow top-level `return` in Astro frontmatter. The core preset now turns off `unicorn/prefer-module` for `**/*.astro` files (the rule cannot be configured to allow only `return`), and keeps `require()`, `module.exports`, `__dirname` and `__filename` flagged there via `import/no-commonjs` and `no-restricted-globals`.

---

# ultracite@7.12.1
Source: https://www.ultracite.ai/changelog/ultracite-7-12-1

## Patch Changes

- 00dd547: Agent hooks now fix only the file the agent edited. The generated hook command passes a new `--hook` flag, and `ultracite fix --hook` reads the agent's payload from stdin: Claude Code and CodeBuddy (`tool_input.file_path`), Cursor (`file_path`) and Windsurf (`tool_info.file_path`). A file outside the project, one that no longer exists, or one the project's linters do not handle is skipped. A payload with no readable file path keeps the previous whole-project run. Re-running `ultracite init` rewrites a hook from an earlier init to the new command, including one generated before this change or for a different package manager or linter.
- 300a814: Update `@biomejs/biome` to 2.5.14. Releases 2.5.13 and 2.5.14 add only nursery rules (14 of them, including `noReturnInFinally`, `noSvelteAtHtmlTags` and `useValidTestTitle`), with no stable-group additions, removals or promotions. The Biome presets deliberately leave nursery rules off, so they are unchanged.
- b8b183b: Update dependencies (`@clack/prompts` 1.8, `empathic` 2.1, `magicast`, `nypm`, `string-width` 8.3, `yaml` and `zod` 4.6).
- b59b8aa: Update oxfmt to 0.70.0 and re-target the markdown `:::` fence patch. Releases 0.68 through 0.70 change no options; they fix suppression-comment handling, comment placement around operators and `as`/`satisfies`, and several YAML and CSS edge cases. oxfmt 0.69 also ships a native markdown formatter, but `.md` files still go through the Prettier-based path, so the fence patch still applies.
- 548c8b0: Update oxlint to 1.85.0. Releases 1.83 through 1.85 add and remove no rules and change no options, so the presets are unchanged. Note that `jest/prefer-strict-equal`, `vitest/prefer-strict-equal`, `vitest/prefer-to-be-truthy` and `vitest/prefer-to-be-falsy` now offer suggestions instead of fixes, so `ultracite fix` reports them rather than rewriting them. `unicorn/consistent-function-scoping` also now catches functions that only capture variables from an outer ancestor scope.
- 0bc6cd6: Update the ESLint family: `eslint` 10.11, `eslint-plugin-unicorn` 76, `@typescript-eslint/*` 8.70.1, `eslint-plugin-jsdoc` 64.5, `eslint-plugin-astro` 3.2, `eslint-plugin-n` 18.4, `eslint-plugin-vue` 10.11.1, `@tanstack/eslint-plugin-query` 5.104, `@next/eslint-plugin-next` 16.3.6, `@darraghor/eslint-plugin-nestjs-typed` 7.5.6, `eslint-plugin-qwik` 1.20.1, `eslint-plugin-html` 8.2.1 and `eslint-plugin-react-doctor` / `oxlint-plugin-react-doctor` 0.9.14.
  
  The ESLint core preset picks up unicorn's ten new JavaScript rules automatically: `no-async-iterator-callback`, `no-unused-builtin-method-return` (which replaces the now-deprecated `no-unused-array-method-return`), `no-unused-iterator-helper`, `no-useless-set-construction`, `no-using-resource-escape`, `prefer-combined-guards`, `prefer-iterator-zip`, `prefer-json-import`, `prefer-temporal-conversion` and `prefer-uint8array-hex`. The CSS-only unicorn rules added in v75 stay off for JavaScript files. unicorn 76 makes `no-immediate-mutation` skip conditional mutations and `no-break-in-nested-loop` skip `continue` by default; the preset keeps those defaults because oxlint's `no-immediate-mutation` behaves the same way and checking `continue` would contradict `prefer-continue`.
- 0bcb2c6: Update `prettier-plugin-astro` to 1.1.0 (the version `ultracite init` installs for Astro projects with Prettier) and refresh the transitive Prettier lock to 3.9.9. Prettier 3.9.7 through 3.9.9 are formatting fixes with no option changes, so the Prettier preset is unchanged. prettier-plugin-astro 1.1 makes `astroAllowShorthand` tri-state. When it is unset, which is how Ultracite's generated config leaves it, attributes now stay as written instead of `{value}` being expanded to `value={value}`. Set `astroAllowShorthand: false` in your Prettier config to keep the 1.0 behaviour.
- 8b39375: Update `@shadcn/lint` to 0.2.0 (the version `ultracite init` installs for the opt-in `ultracite/oxlint/shadcn` preset). The release adds Vue and Svelte support and fixes theme, barrel and class-site discovery; the rules and their options are unchanged, so the preset is too. Under Oxlint the plugin reads only the `<script>` blocks of `.vue` and `.svelte` files, not their templates.
- 0bc6cd6: Update `eslint-plugin-sonarjs` to 4.2.1. The ESLint preset adopts its 16 new rules automatically (Vue, Cypress, Playwright, Testing Library, Vitest, Lodash, jQuery and Axios checks). The `ultracite/oxlint/js-plugins` preset now enables every sonarjs rule that does not need type information, adding 35 rules. These include the 15 new non-type-aware rules and nine test rules that older versions of oxlint's JS plugin bridge could not load. sonarjs 4.2.1 also raised the `no-nested-functions` default threshold from 4 to 5; both presets pin `threshold: 4` to keep the previous strictness.

---

# ultracite@7.12.2
Source: https://www.ultracite.ai/changelog/ultracite-7-12-2

## Patch Changes

- 0f192a7: `ultracite init` no longer wipes an existing Biome config it can't read. Previously a `biome.json` or `biome.jsonc` with a syntax error, or a nested monorepo config with `"extends": "//"`, was treated as empty and replaced with just the Ultracite `extends`, losing every other setting. Now:
  
  - A config with a syntax error is left unchanged, with a warning asking you to fix it and re-run `init`.
  - A nested config that extends the root config (`"extends": "//"`) is left unchanged, since the Ultracite presets belong in the root config.
  - A string `extends` is turned into a list that also includes the Ultracite presets.
  - Updates edit the file in place, so comments and formatting in `biome.jsonc` are preserved.
  
  `ultracite doctor` and the `check`/`fix` resolution check now follow a nested config that extends `"//"` to the root config, instead of warning that the nested config doesn't extend `ultracite/biome/core`.
- c68ba48: `ultracite check` and `ultracite fix` handle their arguments and missing tools more reliably:
  
  - `check` now treats explicit files the way `fix` does. Oxlint only gets files it can lint, Prettier runs with `--ignore-unknown`, and oxfmt with `--no-error-on-unmatched-pattern`. Before, `ultracite check README.md` or `ultracite check Dockerfile src/index.ts` failed even though nothing was wrong.
  - Linter flags that take a value keep it, even when the value looks like a file: `--tsconfig tsconfig.json`, `-c .oxlintrc.json`, `--config-path biome.json`, `--only lint/suspicious/noDebugger`, `--since origin/main` and similar. Before, the value was treated as a lint target, so `ultracite fix --tsconfig tsconfig.json` skipped Oxlint entirely and only formatted `tsconfig.json`. Ultracite's own `--claude`, `--codex`, `--hook` and `--unsafe` never take a value, so the next argument is always a target.
  - `ultracite fix --unsafe` with the ESLint toolchain no longer fails with ESLint's "Invalid option '--unsafe'". ESLint has no unsafe fixes, so the flag is dropped with a warning.
  - A linter that isn't installed is reported with a plain message instead of a stack trace. The other tools still run first. Stylelint is optional in the ESLint toolchain, as `ultracite doctor` already said, so a project without it now skips CSS linting with a warning instead of failing. "No linter configuration found" is also printed without a stack trace.
  - Linters installed in the project's `node_modules/.bin` are found even when Ultracite isn't run through a package manager script, `npx` or `bunx`, for example `./node_modules/.bin/ultracite check`.
- f61f393: `ultracite init` now looks for existing ESLint, Prettier and Stylelint configs in the same order the tools do, so when a project has more than one, init updates the one the tool actually loads. For example, Prettier reads `.prettierrc.json` before `prettier.config.mjs`, and ESLint reads `eslint.config.js` before `eslint.config.mjs`. Before, init could update a config the tool ignored and leave the active one in place. Stylelint's `.stylelintrc.ts` and `stylelint.config.ts` are now recognised too.
- 242cd2a: `ultracite init` now updates an existing `.vscode/settings.json` or `.zed/settings.json` in place, so your comments and formatting are kept. Before, the file was re-serialised as plain JSON, which stripped every comment. A settings file with a syntax error is now left unchanged with a warning. Before, it was rewritten with whatever part the parser could recover, which dropped the rest.
  
  For the ESLint toolchain, init now also installs the Prettier VS Code extension (`esbenp.prettier-vscode`), since the settings it writes make Prettier the default formatter. Before, only the ESLint extension was installed, so format-on-save did nothing until you added Prettier yourself.
- c273393: `ultracite init` now checks every flag value before it changes anything in the project. An unknown value for `--linter`, `--pm`, `--frameworks`, `--editors`, `--agents`, `--hooks`, `--integrations` or `--js-plugins` stops init with a message listing the valid values. Previously a misspelled `--linter` (for example `--linter Biome`) deleted every existing Biome, ESLint, Prettier, Stylelint, Oxlint and oxfmt config file and then crashed.
  
  When `--linter` is not passed and init runs without prompts (because of `--quiet`, `CI`, or flags such as `--agents` or `--pm`), it now keeps the linter the project is already set up with and only falls back to Oxlint when there is none. Running `ultracite init --agents universal` on a Biome project no longer migrates it to Oxlint. The interactive linter prompt also preselects the detected linter.
- 3cb2e71: Clearer wording in the CLI:
  
  - `ultracite init --help` now lists the valid values for `--pm`, `--linter`, `--frameworks`, `--hooks` and `--integrations`, and explains what `--type-aware` does for Biome and for Oxlint.
  - The agent rules file says "Oxlint + Oxfmt will catch most mechanical issues automatically" instead of "Oxlint + Oxfmt's linter will catch…".
  - `init` and `upgrade` say "Using pnpm (detected from the project)" instead of "Detected lockfile", since the package manager can also come from `packageManager`.
  - `ultracite doctor` spells "unrecognized" consistently, formats commands as code, and describes warnings as "Some checks have warnings" instead of "optional improvements".
- 6ae8be8: The ESLint `nestjs` preset imports `@darraghor/eslint-plugin-nestjs-typed`, but `ultracite init --linter eslint --frameworks nestjs` never installed it, so ESLint failed to load the config with "Cannot find package". `init` now installs the plugin with the preset, and `ultracite upgrade` installs the plugins of every framework preset your `eslint.config.*` imports, so existing NestJS projects pick it up on their next upgrade.
- a8e83bb: `ultracite init` now migrates an existing `.oxlintrc.json`, `.oxfmtrc.json` or `.oxfmtrc.jsonc` when it sets up Oxlint. Oxlint and oxfmt refuse to load any config when a JSON config sits next to `oxlint.config.ts` or `oxfmt.config.ts`, and init used to write the TS configs beside the JSON ones, so `ultracite check` and `ultracite fix` stopped working. Init now moves the JSON config's settings into the TS config and deletes the JSON file:
  
  - `rules`, `overrides`, `env`, `plugins` and other options become properties of the generated config.
  - `ignorePatterns`, `settings` and `jsPlugins` are added to the ones Ultracite generates instead of replacing them.
  - Ultracite `extends` entries become presets. Other `extends` paths can't be referenced from a TS config, so init names them in a warning.
  
  A JSON config that doesn't parse is left in place, and neither file is written.
  
  Re-running `ultracite init` also keeps what you added to `oxlint.config.ts` and `oxfmt.config.ts`: custom `rules`, `overrides`, `ignorePatterns`, `settings` and other properties, extra `extends` entries, your own imports and statements, and comments are carried over while the Ultracite parts are regenerated. Before, both files were regenerated from scratch. A config that doesn't parse is now left unchanged with a warning instead of being overwritten.
  
  `ultracite doctor` now fails when a JSON config and a TS config for Oxlint or oxfmt sit side by side, and suggests running `init` to migrate a lone `.oxfmtrc.json`.
- 981ef2f: `ultracite init --linter oxlint` no longer adds `"type": "module"` to `package.json`. That field changes how Node loads every `.js` file in the package, so CommonJS files such as a `next.config.js`, `postcss.config.js` or `jest.config.js` using `module.exports` stopped working after init.
  
  Instead, init writes the Oxlint and oxfmt configs as `oxlint.config.mts` and `oxfmt.config.mts` when the package isn't an ES module package (no `"type"` or `"type": "commonjs"`). A `.mts` file always loads as an ES module, with no `MODULE_TYPELESS_PACKAGE_JSON` warning on every run, and it works under `"type": "commonjs"`. ES module packages (`"type": "module"`) still get `oxlint.config.ts` and `oxfmt.config.ts`.
  
  Re-running init updates an existing config under the name it already has. The one exception is a `.ts` config in a `"type": "commonjs"` package, which Node can't load: init renames it to `.mts` and says so. `ultracite doctor`, linter detection and the stale-config cleanup all recognise the `.mts` names. `doctor` fails a `.ts` config in a CommonJS package, and fails when a `.ts` and an `.mts` config sit side by side.
  
  Requires oxfmt >= 0.59.0, the first release that finds `oxfmt.config.mts` on its own.
- 9a9beb0: `ultracite init` is gentler with `package.json`:
  
  - It keeps the file's key order, indentation and line endings. Before, every write moved `devDependencies` to the top and pushed keys like `private`, `main` and `exports` to the end.
  - It no longer overwrites a `check` or `fix` script the project already has (for example `"check": "tsc --noEmit"`). It prints a warning instead, and it only adds the scripts that are missing. Existing scripts that already run Ultracite with extra flags are left as they are.
  - When switching linters, it only removes the previous linter's packages from `devDependencies`. Packages in `dependencies` and `peerDependencies` stay, such as `prettier` used at runtime or `eslint` as the peer of a published plugin.
  - With `--skip-install`, the final message now says the dependencies were added to `package.json` instead of claiming they were installed.
- c3027a5: Re-running `ultracite init` no longer silently discards changes to an ESLint, Prettier or Stylelint config that builds on Ultracite's:
  
  - `eslint.config.*`: the framework presets it already spreads are kept alongside any newly selected ones, together with your own config objects, imports and a `defineConfig(...)` wrapper. Before, the file was regenerated from the selected frameworks only, dropping earlier presets and every custom rule.
  - `prettier.config.*`: your options, imports and extra plugins are kept. Framework plugins are added, and `prettier-plugin-tailwindcss` stays last.
  - Stylelint: a config that already uses `ultracite/stylelint`, including one in `package.json`, is left as it is.
  
  A config that doesn't use Ultracite's presets is still replaced, but init now prints a warning naming the file (or the `package.json` key) it replaced. A config that doesn't parse is left unchanged with a warning. With the ESLint toolchain, a `"prettier"` or `"stylelint"` key in `package.json` is now handled by these updates (and reported when replaced) instead of being deleted silently during migration.
- 44d6997: `ultracite init` no longer creates directories for agent rule files or agent hook configs (such as `.claude/` or `.cursor/`) before checking that the path stays inside the project. When one of those directories was a symlink to somewhere outside the project, init created the missing directories there before it refused to write the file.
- 33a1ccd: `ultracite init --integrations husky --skip-install` no longer replaces an existing `prepare` script in `package.json`. It adds `husky` to the script, as the installing path already did (for example `"prepare": "svelte-kit sync && husky"`). The Lefthook setup messages now name the config file init actually updates or creates, such as `.lefthook.yaml`, instead of always saying `lefthook.yml`.
- 923667b: `ultracite init` no longer overrides a tsconfig that turns `strictNullChecks` off. It leaves an explicit `"strictNullChecks": false`, whether set in the file or in a config it extends, as it is and prints a warning. It also follows `extends`, whether a relative path or a package such as `@tsconfig/strictest`, so a tsconfig that already inherits `strict` or `strictNullChecks` is no longer given a redundant `"strictNullChecks": true`.
- 199974c: `ultracite init` and `ultracite upgrade` now work in Yarn 2+ monorepos. The root install used to pass Yarn 1's `-W` flag, which Yarn 2+ rejects with "Unsupported option name", whenever the Yarn version wasn't named in `package.json`'s `packageManager` field. That happened with `--pm yarn`, with lockfile-only detection, and always in the second half of `upgrade`, which re-ran the new CLI with a bare `--pm yarn`. Ultracite now tells Yarn 2+ apart from Yarn 1 by `.yarnrc.yml` or the lockfile format. `upgrade` only forwards `--pm` to the newly installed CLI when you passed it.
  
  `ultracite doctor` (and the check at the end of `upgrade`) no longer fails in Yarn Plug'n'Play projects just because it can't find Ultracite or the tools in `node_modules`. It warns that it can't verify them there instead.
- c33158d: Agent hooks set up by `ultracite init --hooks` work in more places and no longer double up.
  
  - **GitHub Copilot:** `.github/hooks/ultracite.json` is now written in the format the Copilot CLI and Copilot cloud agent read: `"version": 1` and a camelCase `postToolUse` event. VS Code reads this format too. The previous file, with a PascalCase `PostToolUse` and no `version`, was only picked up by VS Code. Re-running init moves an existing Ultracite hook to the new format instead of keeping both.
  - **`fix --hook` with Copilot:** the file path is now read from Copilot payloads: `toolArgs.path` from the Copilot CLI (including when `toolArgs` is a JSON string), `tool_input.filePath` from VS Code's edit tools, every file of a `multi_replace_string_in_file` edit, and the file headers of an `apply_patch`. So only the edited files are fixed, not the whole project. These hosts run the hook after every tool, so tools that edit nothing (such as `read_file`, `view` or `bash`) now skip the fix instead of fixing the whole project.
  - **Re-running init no longer adds a second hook** next to one generated by Ultracite 7.8.2 or earlier: `pnpm fix …`, `bun fix …`, `yarn fix …`, or `npm run fix --skip=…`. That older hook is updated in place, so it stops running a whole-project fix after every edit.
  - **A hook is now added** even when the settings file mentions `ultracite` somewhere else, such as a Claude Code permission rule like `Bash(npx ultracite check)`. Only existing hook commands are checked.
  - `fix --hook` now fixes a file at the project root whose name starts with `..`, instead of treating it as outside the project.
  - **Zed:** the `includePackageJsonAutoImports` preference is now set for vtsls, Zed's default TypeScript and JavaScript language server (`lsp.vtsls.settings`), for both TypeScript and JavaScript. It was previously set under `typescript-language-server`, which Zed doesn't use by default.
- dc5e18e: Re-running `ultracite init` now updates the Ultracite rules in `AGENTS.md`, `.claude/CLAUDE.md`, `GEMINI.md` and the other shared rule files in place, instead of appending another full copy.
  
  - Previously a copy was appended whenever the linter, the package manager or the rules text changed. For example, switching from Biome to Oxlint left instructions for both engines side by side. Duplicate copies written by earlier versions are now removed, and your own content before and after the block is kept.
  - Files with CRLF line endings keep them, and are no longer duplicated on every run.
  - The commands in the rules now run the project's installed CLI (`npx ultracite fix`, `yarn ultracite fix`, `pnpm exec ultracite fix`, `bunx ultracite fix`) instead of a dlx runner. For Deno they read `deno run -A npm:ultracite fix`; previously the broken `deno run -A npm: ultracite fix` was written.
  - **Firebender:** rules are now written to `.firebender/rules/ultracite.mdc` with `alwaysApply: true`, where Firebender reads project rules. They were previously written as Markdown into `firebender.json`, which made that file invalid JSON and overwrote an existing Firebender config. A `firebender.json` that still holds only those Markdown rules is reset to `{}`.
- 2ad7704: Fixes for `ultracite fix --claude` and `ultracite fix --codex`:
  
  - On a terminal, the ✓/✗ result for every issue is now kept once a file is done. Previously a file with more issues than the terminal had rows kept only the last screenful of results.
  - In CI logs and other piped output, lint messages are no longer cut off at 80 columns.
  - The prompt is now sent to the agent CLI on stdin (`claude -p`, `codex exec -`) instead of as a command-line argument. On Windows, an npm-installed CLI runs through a `.cmd` shim, which can cut an argument off at its first newline, so the agent received only the prompt's first line and never saw the file or its issues.
  - `--codex` now passes `--skip-git-repo-check`, so it also works in a project that isn't a git repository. Previously `codex exec` refused to run there and every file failed.
- 0b0775e: The Husky pre-commit hook written by `ultracite init --integrations husky` is more robust.
  
  - The hook now runs the project's installed tools (`npx`, `yarn`, `pnpm exec`, `bunx`) instead of `yarn dlx` / `pnpm dlx`. `yarn dlx` does not exist in Yarn 1, so every commit failed with "Ultracite found issues that could not be auto-fixed", and `pnpm dlx` downloaded the latest release instead of the version the project pins. Husky itself is also initialised with the installed binary.
  - Installing Husky now chains `husky` onto an existing `prepare` script (for example SvelteKit's `svelte-kit sync || echo ''`) instead of replacing it. Choosing Husky and lefthook together no longer leaves only one of them in `prepare`.
  - When nothing is staged, the hook no longer exits early, so commands you keep after the Ultracite section still run.
  - Re-running init replaces the Ultracite section of a hook saved with CRLF line endings instead of appending a second one. It also no longer drops the last line of a hook that only mentions "# ultracite" in a comment. Commands after a lint-staged section written by an older version are kept.
- 3862221: `ultracite init --integrations lint-staged` no longer damages or shadows an existing lint-staged config.
  
  - An extension-less `.lintstagedrc` written in YAML (which is how lint-staged reads it) is now edited as YAML. Previously it was overwritten with a JSON file holding only the Ultracite task, deleting the user's own tasks, and single-quoted YAML was silently skipped.
  - YAML configs are edited through the `yaml` Document API, so comments and the rest of the file are kept.
  - TypeScript configs (`.lintstagedrc.ts`, `.mts`, `.cts` and `lint-staged.config.ts`, `.mts`, `.cts`) and the `lint-staged` key of `package.yaml` are now recognised. Previously init created a `.lintstagedrc.json` next to them, and because lint-staged uses only the first config in a directory, the user's config silently stopped running.
  - When a config can't be edited automatically (a function-based entry, a CommonJS module that can't be loaded, a syntax error), init now leaves it untouched and prints the command to add, instead of writing a second config file that would replace it.
  - When both exist, the dedicated config file is updated rather than the `package.json` key, matching the file lint-staged actually uses.
  - A single command already mapped to the same glob is kept alongside `ultracite fix` instead of being replaced.
  - The task now runs the project's installed Ultracite (`npx`, `yarn`, `pnpm exec`, `bunx`) instead of `yarn dlx` / `pnpm dlx`, which don't exist in Yarn 1 or download the latest release instead of the pinned one. Re-running init upgrades a `dlx` command written by an earlier version.
- bffb8dd: Corrected the bundled Ultracite agent skill (`skills/ultracite/SKILL.md`):
  
  - It said Oxlint has `github` and `sonarjs` presets that init includes by default. Neither exists. The GitHub, SonarJS and React Doctor rules live in the `ultracite/oxlint/js-plugins` preset (plus `next/js-plugins` and `tanstack/js-plugins`), next to the `anti-slop` and `shadcn` presets, and all of them are opt-in.
  - The `--js-plugins` init flag is now documented.
  - The skill now tells agents to run the project's installed CLI (`npx`, `pnpm exec`, `yarn`, `bunx`) rather than `pnpx` or `yarn dlx`.
- da2934a: Installing the Ultracite skill from `ultracite init` now works when init runs in a normal terminal.
  
  Init runs `skills add haydenbleasel/ultracite` without a terminal attached. When the `skills` CLI needed to ask which agents to install to, or whether to install into the project or globally, it could not show the prompt:
  
  - In some cases it cancelled the prompt and exited successfully with nothing installed, so init said "Ultracite skill installed." when the skill wasn't there.
  - In others it failed, so the install never happened.
  
  Init now passes `--yes` and names the agents to install for, so `skills` installs without asking. The skill always goes to the shared `.agents/skills` directory, which Codex, Cursor, GitHub Copilot, Gemini CLI, Amp, Cline, OpenCode and other agents read. It also goes to the skills directory of any agent whose project folder exists (for example `.claude`, `.windsurf`, `.codebuddy` or `.roo`, which init creates when you choose those agents).
  
  Init names the agents because otherwise, in a project where `skills` detects no agent, `--yes` would install for every agent it knows. That also created a `.claude/skills` link and a second copy in a top-level `agent/` directory (for the Eve framework). The "install it later" hint still shows the interactive `skills add haydenbleasel/ultracite` command.
- 4941883: `ultracite init` now edits `.pre-commit-config.yaml` and lefthook configs through the `yaml` Document API instead of splicing text, so the result is always valid YAML and comments are kept.
  
  - **pre-commit:** a `repos:` list written flush with its key (`-   repo:`, the style `pre-commit sample-config` generates) or with four-space indentation no longer turns into invalid YAML that breaks every commit. The file's sequence style is kept.
  - **lefthook:** a four-space indented `pre-commit:` block, a compact `jobs:` list, or a column-0 comment inside the block no longer produce invalid YAML or a duplicate `jobs:` key. A hook that uses `commands:` gets a `jobs:` list next to it.
  - **lefthook:** init now finds an existing `.lefthook.yml`, `lefthook.yaml`, `.config/lefthook.yml` (and the other names lefthook reads) and edits it. Previously it created `lefthook.yml`, which lefthook picks first, so the user's own config silently stopped running. A JSON or TOML config is left alone with instructions.
  - **lefthook:** the job's globs are now `*.js`, `*.ts`, and so on. With lefthook's default matcher, the previous `**/*.js` form skipped root-level files such as `package.json` or `index.ts`. Projects that set `glob_matcher: doublestar` get `**/*.js`.
  - **lefthook:** re-running init with a different package manager updates the existing job instead of adding a second one.
  - Both now run the project's installed Ultracite (`npx`, `yarn`, `pnpm exec`, `bunx`) instead of `yarn dlx` / `pnpm dlx`. Re-running init upgrades a hook or job written by an earlier version.
  - `lefthook install` runs the project's installed lefthook, and the `prepare` script is chained onto an existing one (e.g. `svelte-kit sync || echo '' && lefthook install`) instead of replacing it.
- 9c30c15: Raise the `oxlint` peer dependency to `^1.82.0`. The core Oxlint preset configures `no-unmodified-loop-condition` with `checkConditionalExpressions`, an option Oxlint 1.79 to 1.81 reject, so those releases failed with "Failed to parse oxlint configuration file" even though the old `^1.79.0` range allowed them. `ultracite doctor` and your package manager now flag the too-old version instead.
  
  Requires oxlint >= 1.82.0
- 47303f4: The Biome `jest` preset now declares Jest's globals (`describe`, `it`, `test`, `expect`, `jest`, `beforeEach` and the rest of `globals.jest`) for test files. Jest injects them without imports, so `noUndeclaredVariables` from the core preset reported every one of them in idiomatic Jest tests. The ESLint `jest` preset already declared them.
  
  The route-file exemptions in the Biome `remix` and `tanstack` presets (`useFilenamingConvention` off in `routes/`) now cover `.js` and `.jsx` route files as well as `.ts` and `.tsx`.
- 8f236ee: The ESLint core preset now lints `.jsx`, `.tsx`, `.mts` and `.cts` files. Its main block previously matched only `.js`, `.mjs`, `.cjs`, `.ts`, `.json` and `.html`, so ESLint skipped `.mts` and `.cts` files entirely ("File ignored because no matching configuration was supplied"), and `.jsx` and `.tsx` files received only the framework preset's rules. `.tsx` files were also parsed by espree, so any TypeScript syntax in them was a parse error. Every TypeScript extension now uses `@typescript-eslint/parser` with type information, and the core rules apply to all of them.
  
  Type information now comes from the TypeScript project service (`parserOptions.projectService: true`) instead of a fixed `project: "./tsconfig.json"`. Solution-style tsconfigs (`"files": []` plus `references`, as in the Vite templates) and monorepo packages now resolve their own tsconfig, where previously every file failed to parse. A file that no tsconfig includes still has to be added to one; typescript-eslint reports it as "not found by the project service" (see https://typescript-eslint.io/troubleshooting/typed-linting/#i-get-errors-telling-me-was-not-found-by-the-project-service-consider-either-including-it-in-the-tsconfigjson-or-including-it-in-allowdefaultproject).
  
  The JavaScript block no longer matches `**/*.json`. espree cannot parse JSON, so every `package.json` and `tsconfig.json` failed with `Parsing error: Unexpected token :`. The ESLint preset does not lint JSON, matching the Oxlint preset.
- 94722fa: The `eslint.config.mjs` that `ultracite init` writes no longer fails its own lint. Every ESLint preset exported a default named `config`, so `import core from "ultracite/eslint/core"` (and each framework import) tripped `import-x/no-rename-default` twice per preset. Each preset's default export is now named after the identifier the generated config imports it as (`core`, `react`, `tanstack`, …).
- d9803a6: Fix ESLint presets that crashed the whole run or never reached the files they target.
  
  - **TanStack:** `@tanstack/start/no-async-client-component` and `@tanstack/start/no-client-code-in-server-component` need type information and aborted ESLint ("You have used a rule which requires type information") on the first `.jsx` or `.tsx` file. They now run only on TypeScript files. The Query, Router and Start rules also apply to plain `.ts`/`.js` modules, where query and mutation options are usually declared, instead of only to `.jsx` and `.tsx`. `sort-keys` is off, and `no-use-before-define` and `unicorn/filename-case` are off in `routes/` directories, matching the Oxlint and Biome TanStack presets (alphabetical option keys break TanStack's type inference, and file routes are mutually recursive and encode the URL in the filename).
  - **Qwik:** `qwik/valid-lexical-scope` needs type information and crashed ESLint on `.jsx` files. It now runs only on `.tsx` files.
  - **Jest:** `jest/no-deprecated-functions` threw "Unable to detect Jest version" and crashed ESLint when the `jest` package was not resolvable from the plugin, for example in bun:test projects. The preset now reads the Jest version from the project and falls back to the latest major.
  - **Cypress:** the block used `globals.cypress`, which does not exist in the `globals` package, so `cy`, `Cypress`, `describe` and `it` were reported by `no-undef`. It now uses `eslint-plugin-cypress`'s own globals config. It also matched only `*.cy.js`, and now covers `*.cy.*` for every JS and TS extension plus files under `cypress/`.
  - **Storybook:** the block matched only `*.stories.js` and `*.stories.ts`. It now covers `*.stories.*` and `*.story.*` for every JS and TS extension, including `.tsx` and `.jsx`.
- d6ee272: The ESLint `vue`, `svelte` and `astro` presets now parse their files. They registered only the plugin and its rules, never a parser, so ESLint read every `.vue`, `.svelte` and `.astro` file with espree and reported a parse error (`Unexpected token <`) instead of linting it.
  
  Each preset now starts from its plugin's own base config (`flat/base` in `eslint-plugin-vue`, `eslint-plugin-svelte` and `eslint-plugin-astro`), which registers `vue-eslint-parser`, `svelte-eslint-parser` or `astro-eslint-parser` from the plugin's dependencies, and parses `<script lang="ts">` blocks with `@typescript-eslint/parser`. The Svelte preset also covers `.svelte.js` and `.svelte.ts` rune modules. In Astro files, client-side `<script>` tags are linted without type information, because those in-memory virtual files cannot be type-checked.
- f7599ef: The ESLint core preset no longer re-enables formatting rules that `eslint-config-prettier` turns off. The unicorn rule set was spread after `eslint-config-prettier`, which switched `unicorn/number-literal-case`, `unicorn/template-indent` and `unicorn/empty-brace-spaces` back on. `unicorn/number-literal-case` demands `0xABCD` while Prettier prints `0xabcd`, so `prettier/prettier` and the unicorn rule reported every hex literal and `eslint --fix` could not satisfy both. `eslint-config-prettier` now applies after every plugin, so `unicorn/number-literal-case` and `unicorn/template-indent` are off. `unicorn/empty-brace-spaces` stays on (Prettier prints empty braces as `{}` too), matching the Oxlint preset.
- efa80e8: The ESLint core preset no longer reports the same problem two or three times on TypeScript files, and no longer flags ambient type-only globals.
  
  - `no-undef` and `sonarjs/no-reference-error` are off for `.ts`, `.tsx`, `.mts` and `.cts` files. TypeScript already reports unresolved identifiers, and both rules flagged valid ambient types such as `NodeJS.Timeout` (see the [typescript-eslint FAQ](https://typescript-eslint.io/troubleshooting/faqs/eslint#i-get-errors-from-the-no-undef-rule-about-global-variables-not-being-defined-even-though-there-are-no-typescript-errors)).
  - The base `class-methods-use-this`, `consistent-return`, `no-unused-private-class-members`, `prefer-destructuring` and `prefer-promise-reject-errors` rules are off for TypeScript files, because their `@typescript-eslint` extension rules are enabled there. The base rules duplicated every report and ignored the extensions' TypeScript-aware options.
  - `unused-imports/no-unused-vars` is off. It is a copy of `no-unused-vars` / `@typescript-eslint/no-unused-vars`, which stay on as in the Oxlint preset, so every unused variable was reported twice. `unused-imports/no-unused-imports` stays on for its autofix.
  - `@typescript-eslint/max-params` is off, matching `max-params` being off in the core presets. It was on with its default limit of 3 parameters for TypeScript files only.
- 9ae95d1: Fix false positives in the ESLint `vue`, `svelte` and `astro` presets that appeared once their files were actually parsed.
  
  - `vue/block-lang` and `svelte/block-lang` rejected every `<script lang="ts">`, because with no options they only allow blocks without a `lang` attribute. They now allow TypeScript scripts, and `less` and `scss` styles, as well as blocks without `lang`.
  - Astro's client-side `<script>` tags are linted as virtual files named `1_1.ts`, `2_1.js` and so on, which `github/filenames-match-regex` reported on every page with a script tag. Filename rules are now off for those virtual files.
  - The Astro preset passes `@typescript-eslint/parser` for the frontmatter explicitly. ESLint's config merge dropped the copy in `eslint-plugin-astro`'s base config, so frontmatter TypeScript parsed only when `@typescript-eslint/parser` happened to resolve from the working directory, and failed with `The keyword 'interface' is reserved` otherwise.
  - `ultracite init` now installs `eslint-plugin-jsx-a11y` for Astro projects using ESLint. The preset enables `eslint-plugin-astro`'s `astro/jsx-a11y/*` rules, which load that package and reported "you need to install eslint-plugin-jsx-a11y" on every `.astro` file when it was missing.
- e88e76d: The Prettier preset now sets `tailwindFunctions` to `clsx`, `cva`, `tw`, `twMerge`, `cn`, `twJoin` and `tv`, so `prettier-plugin-tailwindcss` sorts Tailwind classes passed to those helpers anywhere in a file, for example `const button = cva("p-4 flex")`. Previously only class strings inside `class`/`className` attributes were sorted with Prettier, while the Oxfmt (`sortTailwindcss.functions`) and Biome (`useSortedClasses`) presets already sorted these helpers. See https://github.com/tailwindlabs/prettier-plugin-tailwindcss#sorting-classes-in-function-calls.
- 3a5885e: `github/filenames-match-regex` now accepts file-based routing filenames in the ESLint preset too, and Next.js's special pages in both presets.
  
  - The page-route regex (Oxlint `js-plugins` and now ESLint `core`) allows a leading underscore, so the Next.js pages-router files `_app`, `_document` and `_error`, which cannot be renamed, are no longer reported. Other names in `pages/` (`BadPage.ts`) and camelCase route params (`[postId]`, which `unicorn/filename-case` rejects too) are still reported.
  - The ESLint `core` preset now carries the same route exemptions as the Oxlint `js-plugins` preset (#799, #804). Previously it applied the plain kebab-case regex everywhere and reported SvelteKit's `+page.ts` and `+server.ts`, TanStack Router and React Router files such as `posts.$postId.ts`, and page routes such as `[slug].json.ts` and `[...auth].ts`.
  - The route-directory exemptions (`github/filenames-match-regex` in Oxlint `js-plugins` and ESLint `core`, plus `unicorn/filename-case` and `no-use-before-define` in the Oxlint and ESLint `tanstack` presets) now cover `.js` and `.jsx` route files as well as `.ts` and `.tsx`.
- ad2adb0: The Stylelint preset now handles Tailwind CSS v4, SCSS and Less, and skips build output.
  
  - **Tailwind CSS v4:** `@theme`, `@utility`, `@variant`, `@custom-variant`, `@slot`, `@plugin` and `@config` are allowed by `at-rule-no-unknown`, alongside the Tailwind v3 at-rules and `@source` and `@reference`. `at-rule-prelude-no-invalid` no longer rejects every `@apply` (or the other Tailwind at-rules' preludes). `custom-property-pattern` accepts theme namespace resets (`--color-*: initial`) and sub-properties (`--text-xl--line-height`). `declaration-property-value-no-unknown` and `function-no-unknown` accept `--spacing()`, `--alpha()`, `--value()`, `--modifier()` and `theme()`. `media-query-no-invalid` accepts `theme()` breakpoints, and `nesting-selector-no-missing-scoping-root` allows `&` inside `@custom-variant`, `@variant` and `@utility`. See https://tailwindcss.com/docs/functions-and-directives.
  - **`import-notation`** is now `"string"`. `stylelint-config-standard`'s `"url"` autofix rewrote `@import "tailwindcss"` to `@import url("tailwindcss")`.
  - **SCSS and Less:** `.scss` files are parsed with `postcss-scss` and `.less` files with `postcss-less`. Previously every SCSS and Less file failed with `CssSyntaxError` (for example on `//` comments or mixin calls). The CSS-only rules that cannot understand preprocessor syntax (unknown at-rules such as `@use`, `@include` and `@mixin`, `$variable` and `@variable` values, Sass and Less built-in functions, `//` comments) are relaxed for those files. `ultracite init` now installs `postcss-scss` and `postcss-less` with the ESLint toolchain.
  - **`.sass`:** the indented Sass syntax has no maintained PostCSS parser, so `ultracite check` and `ultracite fix` no longer pass `.sass` files to Stylelint, where every one failed to parse.
  - **Ignores:** `ignoreFiles` now uses the shared ignore list (`dist`, `build`, `.next`, `coverage`, `storybook-static` and so on). Stylelint does not read `.gitignore`, so it previously linted generated CSS.
  - **Prettier:** `prettier/prettier` is now enabled. The preset loaded `stylelint-prettier` but never turned its rule on.
  - `ultracite check` and `ultracite fix` now escape glob characters in directory arguments before passing them to Stylelint. A directory such as `app/(marketing)` previously matched no files.
- 89989df: Test-file overrides in every preset now match `.mts`, `.cts`, `.mjs` and `.cjs` test files as well as `.ts`, `.tsx`, `.js` and `.jsx`. The globs were `**/*.{test,spec,test-d,spec-d}.{ts,tsx,js,jsx}` and `**/__tests__/**/*.{ts,tsx,js,jsx}`, so a `sum.test.mts` file got none of the test-file relaxations and none of the Jest or Vitest rules. For example, `test.only` in a `.test.mts` file was not reported by `vitest/no-focused-tests` or `jest/no-focused-tests`. This covers the Oxlint `core`, `js-plugins`, `jest` and `vitest` presets, the Biome `core` preset, and the ESLint `core`, `jest` and `vitest` presets.
- 4d28cf9: The Oxlint `vue` preset now lists every non-nursery Vue rule Oxlint implements, like the other framework presets. It previously enabled 18 of them. Among the 27 newly enabled rules are `vue/valid-define-props`, `vue/valid-define-emits`, `vue/no-export-in-script-setup`, `vue/no-lifecycle-after-await`, `vue/no-arrow-functions-in-watch`, `vue/no-side-effects-in-computed-properties`, `vue/require-typed-ref`, `vue/define-props-destructuring` and the `vue/no-deprecated-*` rules. `vue/max-props` is off in both the Oxlint and ESLint presets, because its default allows a single prop per component.
  
  The Oxlint `vitest` preset now enables `vitest/consistent-test-it`, the one Vitest rule it was missing (the ESLint preset already had it).
  
  Vue files whose names Nuxt and file-based Vue Router require (`pages/**`, `layouts/**`, `error.vue` and `app.vue`) are exempt from `useVueMultiWordComponentNames` in the Biome preset and from `vue/multi-word-component-names` in the ESLint preset. Previously `pages/index.vue`, `layouts/default.vue` and `error.vue` were always reported.

---

# ultracite@7.12.3
Source: https://www.ultracite.ai/changelog/ultracite-7-12-3

## Patch Changes

- f753c14: Add opt-in TSDoc syntax validation and public TypeScript API documentation checks to the Oxlint `js-plugins` preset. Selecting a plugin with `--js-plugins` on a config that extends the full `js-plugins` preset now keeps the preset's plugins.
- ade34d3: Update `@biomejs/biome` to 2.5.15. The release adds 11 nursery rules and changes no stable rules, so the Biome presets, which exclude nursery rules, are unchanged. It speeds up HTML formatting and big-file analysis, fixes Astro expression indentation and Svelte comment placement, and reports configuration errors that Biome 2.5.14 silently ignored.
- 631e0dd: Update oxfmt to 0.71.0. The release changes no options; it bundles Prettier 3.9.9 for embedded languages and fixes comment placement around assignments, JSDoc alignment and several Markdown edge cases.
- 08e83af: Update oxlint to 1.86.0 and enable its new type-aware rule, [`typescript/no-generated-empty-object-type`](https://oxc.rs/docs/guide/usage/linter/rules/typescript/no-generated-empty-object-type.html), in the core Oxlint preset. It reports type operations such as `Pick<Data, never>` that resolve to the empty object type `{}`, matching the `@typescript-eslint` rule of the same name that the ESLint preset already enables. Like the other type-aware rules, it only runs with `oxlint --type-aware` and `oxlint-tsgolint` installed. Older oxlint releases fail to parse a config that names the rule, so the `oxlint` peer range moves to `^1.86.0`.
  
  Requires oxlint >= 1.86.0
- 2a9348c: Update the ESLint presets' plugins: `eslint` 10.12, `eslint-plugin-unicorn` 77, `eslint-plugin-jsdoc` 65, `@typescript-eslint` 8.71, `eslint-plugin-sonarjs` 4.2.2, `eslint-plugin-react-doctor` and `oxlint-plugin-react-doctor` 0.9.16, plus patch releases of the Next.js, TanStack Query, `n`, Solid and Storybook plugins.
  
  The ESLint core preset enables every non-deprecated JavaScript rule from unicorn, so it now also runs unicorn 77's 21 new JavaScript rules, including [`no-unnecessary-parameters`](https://github.com/sindresorhus/eslint-plugin-unicorn/blob/v77.0.0/docs/rules/no-unnecessary-parameters.md), [`no-unsafe-json-serialization`](https://github.com/sindresorhus/eslint-plugin-unicorn/blob/v77.0.0/docs/rules/no-unsafe-json-serialization.md), [`prefer-promise-static-methods`](https://github.com/sindresorhus/eslint-plugin-unicorn/blob/v77.0.0/docs/rules/prefer-promise-static-methods.md) and a set of `no-invalid-*` checks for DOM, `Intl`, `Response`, Temporal and property descriptor arguments. It also enables the new type-aware [`@typescript-eslint/no-unsafe-enum-assignment`](https://typescript-eslint.io/rules/no-unsafe-enum-assignment). Unicorn 77 moves its CSS-only rules to `eslint-cssicorn`; the preset never enabled them for JavaScript files, so nothing is lost.
- 864cde1: Raise the `eslint` peer dependency to `^10.9.0`. The ESLint core preset configures `no-unmodified-loop-condition` with `checkConditionalExpressions`, an option ESLint 10.0 to 10.8 reject, so every preset except Vue failed with `Key "rules": Key "no-unmodified-loop-condition"` on those releases even though the old `^10.0.0` range allowed them (`eslint-plugin-unicorn` also needs ESLint 10.4 or later). `ultracite init` and `ultracite upgrade` now install a release that loads the presets, and `ultracite doctor` and your package manager flag older ones. `@eslint/js`, which is no longer versioned with ESLint, keeps its own `^10.0.1` range.
  
  Requires eslint >= 10.9.0
- d7563b3: `ultracite init` now skips every prompt when you pass any of `--pm`, `--editors`, `--agents`, `--hooks`, `--integrations`, `--frameworks` or `--workspace-framework`, as documented. Before, the editor, agent, hook, skill and (with `--frameworks`) integration prompts still asked, which stalled scaffolding tools that call init without a TTY. `--js-plugins` with a linter other than Oxlint now stops init with an error instead of being silently ignored, and without `--linter` it skips the linter prompt.
- 6c7e149: `ultracite init` no longer hangs on a `.pre-commit-config.yaml` or lefthook config with CRLF line endings and many consecutive comment lines. The check that keeps the file's sequence indentation could backtrack exponentially on that input.
- 3dc6431: On Windows, a linter or formatter that isn't installed is now reported as missing instead of as "exited with code 1". `ultracite check` and `ultracite fix` warn and skip CSS linting when the optional Stylelint is missing, as they already did on macOS and Linux, and `ultracite fix --agent` now skips a missing Stylelint on every platform instead of failing.
- 7f085b2: Type `jsPlugins` as a non-null array on the Oxlint presets that always ship plugins (`js-plugins`, `shadcn`, `anti-slop`, `next/js-plugins`, `tanstack/js-plugins`) and on `selectJsPlugins()`'s return value, so spreading several of them into a root `jsPlugins` array typechecks.
- 45e7f86: The ESLint core preset enables `unicorn/prefer-combined-guards`'s new [`checkMultiStatementBodies`](https://github.com/sindresorhus/eslint-plugin-unicorn/blob/v77.0.0/docs/rules/prefer-combined-guards.md#checkmultistatementbodies) option, so consecutive guards whose bodies repeat the same statements before the same exit (for example, two `if` blocks that each log and `continue`) are reported and can be combined with `||`. In TypeScript, the rule only combines bodies when type information shows every reference has the same type in both.
- d5523c5: `ultracite init` takes `--workspace-framework <path>=<framework>` for monorepos whose workspaces use different frameworks. For each workspace, it writes an Oxlint, Biome or ESLint config in that directory that extends the root config and adds the workspace's presets, so framework rules only run where they apply and editors see the same rules as `ultracite check`.

---

# ultracite@7.12.4
Source: https://www.ultracite.ai/changelog/ultracite-7-12-4

## Patch Changes

- 1cdaf87: Add opt-in `ultracite/oxlint/gdp` and `ultracite/eslint/gdp` presets for [gdp-ts](https://github.com/rauchg/gdp-ts), which makes authorization checks visible to the type checker. Following upstream's strict mode, they stop proofs being forged with type assertions (`{} as UserIsProjectAdmin<U, P>`) or minted outside `proofs/`, ban other type assertions outside `proofs/` and `lib/ids.ts` (except `as const`), and keep provers private to their trusted module. Upstream's `no-any` is left off because core already bans `any`. Inside `proofs/`, empty proof interfaces (`interface X<P> extends Proof<"X", [P]> {}`) are allowed, and the ESLint preset ignores `_`-prefixed proof arguments in `no-unused-vars`, as Oxlint does by default. `@gdp-ts/core` ships the plugin, so there is nothing extra to install: extend the preset after `core`.

---

# ultracite@7.2.0
Source: https://www.ultracite.ai/changelog/ultracite-7-2-0

## Minor Changes

-   fe9acf6: Use local binaries

## Patch Changes

-   357be7e: Store full package manager info from detectPackageManager()
-   8666788: Fix Husky precommit hook

---

# ultracite@7.2.1
Source: https://www.ultracite.ai/changelog/ultracite-7-2-1

## Patch Changes

-   0d21c46: Restore shell for windows

---

# ultracite@7.2.2
Source: https://www.ultracite.ai/changelog/ultracite-7-2-2

## Patch Changes

-   8db75d7: Only run shell: true on windows

---

# ultracite@7.2.3
Source: https://www.ultracite.ai/changelog/ultracite-7-2-3

## Patch Changes

-   3cd6e7b: Upgrade Biome to 2.4

---

# ultracite@7.2.4
Source: https://www.ultracite.ai/changelog/ultracite-7-2-4

## Patch Changes

-   cfaa912: Remove Jest and Vitest rules from non-test files
-   f72f2dc: Add support for copilot hooks
-   66d51fd: Disable import/no-nodejs-modules for Chris Consent
-   d1e8490: Create skill

---

# ultracite@7.2.5
Source: https://www.ultracite.ai/changelog/ultracite-7-2-5

## Patch Changes

-   83bafe4: Disable useValidLang rule for SvelteKit app.html to prevent false positives from %lang% placeholder
-   4df6da9: Disable noUndeclaredVariables for Svelte files to fix false positives with template block variables like {#each}

---

# ultracite@7.3.0
Source: https://www.ultracite.ai/changelog/ultracite-7-3-0

## Minor Changes

-   0d27e68: fix noUnusedImports removing new imports in agent hooks

## Patch Changes

-   668fe62: Add --type-aware flag for biome
-   4280484: Disable max-statements in Oxlint
-   d37b046: Disable jsdoc/require-param-type and jsdoc/require-returns-type for TS files

---

# ultracite@7.3.1
Source: https://www.ultracite.ai/changelog/ultracite-7-3-1

## Patch Changes

-   f84edff: Fix --type-aware for Biome
-   acf301c: Migrate from eslint-plugin-import to import-x
-   5749eb1: Create test frameworks

---

# ultracite@7.3.2
Source: https://www.ultracite.ai/changelog/ultracite-7-3-2

## Patch Changes

-   8ffeb33: Add support for .oxlintrc.mjs and oxlint.config.ts

---

# ultracite@7.4.0
Source: https://www.ultracite.ai/changelog/ultracite-7-4-0

## Minor Changes

-   c189cf1: Add support for new agent integrations including Zencoder, Ona, OpenClaw, Continue, Snowflake Cortex, Deepagents, Qoder, Kimi CLI, Kode, MCPJam, Mux, Pi, Neovate, Pochi, and AdaL, plus add CodeBuddy as a supported editor.

## Patch Changes

-   04d8455: Add no-void rule with allowAsStatement to complement no-floating-promises
-   e38d579: Fix DEP0190 deprecation warnings in `check`, `fix`, and `doctor` by routing CLI subprocesses through a shared `cross-spawn` runner with `shell: false`, while preserving Windows command resolution and direct file-path argument passing.
-   98cb8c2: Pin ESLint initialization to a peer-compatible dependency set so `ultracite init` no longer installs an incompatible `eslint@latest` with `eslint-plugin-github`
-   fd7d05f: Disable conflicting `vitest/prefer-called-times` oxlint rule to resolve conflict with `vitest/prefer-called-once`
-   581ea40: Add typed `ultracite/oxlint` exports for use in `oxlint.config.ts`.

---

# ultracite@7.4.2
Source: https://www.ultracite.ai/changelog/ultracite-7-4-2

## Patch Changes

-   94e770e: Remove non-existent oxlint rules (`import/no-unresolved`, `vitest/no-done-callback`) for compatibility with oxlint 1.58.0+

---

# ultracite@7.4.3
Source: https://www.ultracite.ai/changelog/ultracite-7-4-3

## Patch Changes

-   42b3552: Update the bundled VS Code settings to use `js/ts.tsdk.path` and `js/ts.tsdk.promptToUseWorkspaceVersion` instead of the deprecated `typescript.tsdk` setting.
-   a0a03c6: Allow `utf-8` values in the `unicorn/text-encoding-identifier-case` rule across the bundled ESLint and Oxlint configs.

---

# ultracite@7.4.4
Source: https://www.ultracite.ai/changelog/ultracite-7-4-4

## Patch Changes

-   e9db6f1: Add IBM Bob agent, editor, and logo
-   5341bcc: Disable vitest/prefer-strict-boolean-matchers to resolve conflict with prefer-to-be-truthy and prefer-to-be-falsy

---

# ultracite@7.5.0
Source: https://www.ultracite.ai/changelog/ultracite-7-5-0

## Minor Changes

-   7861cf7: Migrate oxlint and oxfmt configurations from JSON to TypeScript using `defineConfig`. The CLI now generates `oxlint.config.ts` and `oxfmt.config.ts` instead of `.oxlintrc.json` and `.oxfmtrc.jsonc`, and all internal framework presets have been converted to TypeScript.

## Patch Changes

-   fdb1493: Exclude package manager lock files (bun.lock, bun.lockb, package-lock.json, yarn.lock, pnpm-lock.yaml) from Biome linting and formatting

---

# ultracite@7.5.1
Source: https://www.ultracite.ai/changelog/ultracite-7-5-1

## Patch Changes

-   e96c55a: Switch oxlint.config.ts to js imports

---

# ultracite@7.5.2
Source: https://www.ultracite.ai/changelog/ultracite-7-5-2

## Patch Changes

-   22df7a5: Fix oxlint import issues

---

# ultracite@7.5.3
Source: https://www.ultracite.ai/changelog/ultracite-7-5-3

## Patch Changes

-   97c3938: Fix oxlint and oxfmt import paths

---

# ultracite@7.5.4
Source: https://www.ultracite.ai/changelog/ultracite-7-5-4

## Patch Changes

-   66999e0: Fix oxlint and oxfmt yet again

---

# ultracite@7.5.5
Source: https://www.ultracite.ai/changelog/ultracite-7-5-5

## Patch Changes

-   5437f81: Attempt to fix oxlint/oxfmt AGAIN

---

# ultracite@7.5.6
Source: https://www.ultracite.ai/changelog/ultracite-7-5-6

## Patch Changes

-   acf4a97: Update oxlint jest rules
-   6905932: Fix vitest/no-importing-vitest-globals conflict
-   4e4dc03: Update oxlint vitest rules
-   6a583d1: Fix oxfmt setup config

---

# ultracite@7.5.7
Source: https://www.ultracite.ai/changelog/ultracite-7-5-7

## Patch Changes

-   a63d9c5: Fix cross-config leaking rules
-   d18d0e7: Configure Prettier with frameworks context
-   1d6de0d: Add declaration files for `ultracite/oxlint/*` and `ultracite/oxfmt` so TypeScript config imports resolve without `ts(7016)` errors.
-   1073f34: Ensure init'ed JSON files have newlines

---

# ultracite@7.5.8
Source: https://www.ultracite.ai/changelog/ultracite-7-5-8

## Patch Changes

-   c35a1b3: Performance improvements - doctor
-   56e4c00: Remove process.exit() - swap with typed Error
-   d35d03c: Performance optimizations - mkdir(), readFile()
-   ee224a6: Use Commander.js args properly
-   a2b7a46: Rework doctor command
-   cf4a044: Fix angular eslint plugin typo
-   25eb24f: Optimize dev dep install
-   b46537a: Performance optimizations - exists()

---

# ultracite@7.5.9
Source: https://www.ultracite.ai/changelog/ultracite-7-5-9

## Patch Changes

-   77e9b41: Aggregate all ignore patterns
-   73fc21c: Code reliability improvements
-   63f7426: Migrate remaining json parsing to jsonc-parser
-   aa199d1: fix conflicting prefer-describe-function-title / valid-title rules in vitest
-   402908e: Replace custom yaml parser with dependency
-   3dbfe5c: Validate framework name to prevent injection
-   a2cdc0f: Warn if the file looks like it has ultracite config but we couldn't parse it
-   95718bb: Use cross-spawn for cross-platform spawn compatibility
-   d09174b: Ignore `.open-next` in the Biome and ESLint core presets.
-   71aeca4: Remove remaining execSync calls
-   e81a604: Add zod for safer json parsing

---

# ultracite@7.6.0
Source: https://www.ultracite.ai/changelog/ultracite-7-6-0

## Minor Changes

-   67227c9: Add new Biome rules
-   f506624: Add new oxlint 1.160.0 rules

## Patch Changes

-   a684c4a: Fix Tanstack Query ESLint plugin import
-   4983eaa: Skip the init skill-install prompt when the Ultracite skill is already installed in the current project or globally.

---

# ultracite@7.6.1
Source: https://www.ultracite.ai/changelog/ultracite-7-6-1

## Patch Changes

-   2fbded9: Disable the `typescript/prefer-readonly-parameter-types` Oxlint rule. While the rule is useful for user-authored types, it fires on virtually every parameter that touches a third-party type (Express `Request`/`Response`, React events, Node `Buffer`, ORM models, DOM APIs) because those types aren't deeply readonly internally — leaving users with unfixable violations. Matches the existing ESLint config, which already has this rule off.
-   617affd: Fix `dist/`, `.next/`, `**/*.gen.*`, and other strong-negation (`!!`) ignore globs being dropped when a consumer's `biome.jsonc` extends `ultracite/biome/core` and also defines its own `files.includes`. The globs moved into `config/shared/ignores.jsonc` in 7.5.9 were transitively extended through `biome/core`, and Biome's extend merge doesn't carry `files.includes` through a two-level chain when the middle config lacks its own entry. The patterns are now inlined directly in `biome/core`'s `files.includes` (still generated from `config/shared/ignores.mjs`), matching the pre-7.5.9 behavior.
-   d681e08: Remove the nonexistent `import-x/enforce-node-protocol-usage` rule from the ESLint core config, which caused ESLint 9 to throw `Could not find "enforce-node-protocol-usage" in plugin "import-x"`. Node protocol enforcement is already covered by `unicorn/prefer-node-protocol`.

---

# ultracite@7.6.2
Source: https://www.ultracite.ai/changelog/ultracite-7-6-2

## Patch Changes

-   5be860c: Automatically detect frameworks during the `init` process.
-   10d9e95: Support `-v` as a short alias for `--version` on the CLI (previously only `-V` worked).
-   8ff1b96: Fix `update` command not migrating legacy `ultracite/<name>` extends entries to `ultracite/biome/<name>` (e.g. `ultracite/core`, `ultracite/react`, `ultracite/type-aware`, etc.).
-   5e055ce: Ignore Cloudflare Workers' generated `worker-configuration.d.ts` (produced by `wrangler types`), matching the existing handling of `next-env.d.ts`.
-   9cc7416: Add a `universal` editor target that creates `.vscode/settings.json` for every VS Code-based editor (VS Code, Cursor, Windsurf, CodeBuddy, Antigravity, IBM Bob, Kiro, Trae, Void) with a single selection. The `init` prompt now offers a "Universal" option, and `--editors universal` works as an alias on the CLI.

---

# ultracite@7.6.3
Source: https://www.ultracite.ai/changelog/ultracite-7-6-3

## Patch Changes

-   f584d93: Disable `unicorn/number-literal-case` due to [oxc-project/oxc#21949](https://github.com/oxc-project/oxc/issues/21949).
-   ef5c3ae: Fix `ultracite check` and `ultracite fix` short-circuiting after the formatter step. Previously, when the formatter (oxfmt or Prettier) exited non-zero, the linter (oxlint, ESLint, Stylelint) was never invoked, hiding lint errors until formatting was clean. The commands now run every step, accumulate failures, and exit with the first failing tool's status. Fixes [#690](https://github.com/haydenbleasel/ultracite/issues/690).
-   3ecb159: Fix the generated `oxfmt.config.ts` template, which used `extends: [ultracite]` — a key oxfmt does not recognize, so the preset was silently dropped and built-in options like `sortImports` never took effect. The template now spreads the preset (`...ultracite`) so its options are actually applied. Fixes [#689](https://github.com/haydenbleasel/ultracite/issues/689).
-   5a18ec8: Add new oxlint 1.61.0 and 1.62.0 rules:

    -   `eslint/func-name-matching` → `"error"` — function names should match the variable they're assigned to; matches the project's strict baseline.
    -   `eslint/no-underscore-dangle` → `"off"` — common patterns like `_id` (Mongo) and `_internal` make this rule too noisy in practice.
    -   `typescript/explicit-member-accessibility` → `"off"` — forcing `public`/`private` on every class member is verbose and not idiomatic in modern TS.
    -   `jest/prefer-expect-assertions` → `"off"` and `vitest/prefer-expect-assertions` → `"off"` — requiring `expect.assertions(n)` in every test is too strict for general use; not all tests need explicit assertion counts.
    -   `vitest/max-expects` → `"error"` and `vitest/max-nested-describe` → `"error"` — newly split out from the jest plugin; mirrors the existing jest config which has both enabled.
    -   `vitest/no-conditional-in-test` → `"off"` — newly split out from jest; disabled to mirror jest config (mock factories use conditionals for path-based routing).
    -   `vitest/no-hooks` → `"off"` — newly split out from jest; disabled to mirror jest config (bun:test uses `beforeEach` for `mock.restore()`).
    -   `react/forbid-component-props` → `"off"` — parity with the ESLint config, which already disables this rule.

---

# ultracite@7.6.4
Source: https://www.ultracite.ai/changelog/ultracite-7-6-4

## Patch Changes

-   aba89bb: Add new oxlint 1.63.0 rules:

    -   `eslint/logical-assignment-operators` → `"error"` — prefer `||=`, `&&=`, `??=` over their longhand equivalents; aligns with the modern-JS baseline.
    -   `eslint/require-unicode-regexp` → `"error"` — require the `u` (or `v`) flag on regex literals for correct Unicode handling.
    -   `eslint/no-restricted-properties` → `"off"` — purely a project-specific allowlist; no useful default to enforce.
    -   `unicorn/no-negated-condition` → `"error"` — newly split from the eslint version; the unicorn variant additionally covers ternary expressions and complements the existing `eslint/no-negated-condition`.
    -   `jsx-a11y/interactive-supports-focus` → `"error"` — interactive elements (click handlers, `role="button"`, etc.) must be keyboard-focusable; matches the rest of the a11y baseline.
    -   `vue/return-in-computed-property` → `"error"` — computed properties must return a value; missing `return` silently breaks reactivity.
    -   `vue/no-deprecated-model-definition` → `"error"` — flags Vue 2 `model: { ... }` usage; Vue 3 is the supported target.
    -   `vitest/prefer-mock-return-shorthand` → `"error"`, `vitest/no-unneeded-async-expect-function` → `"error"`, `vitest/prefer-to-have-been-called-times` → `"error"`, `vitest/prefer-snapshot-hint` → `"error"` — newly split out from the jest plugin; mirrors the existing jest config which has all four enabled.
    -   `vitest/require-hook` → `"off"` — newly split out from jest; disabled to mirror jest config (bun:test `mock.module()` must be called at top level).

-   522155e: Set `typescript/return-await` to `["error", "always"]` to resolve a circular conflict between `eslint/require-await`, `typescript/promise-function-async`, and `typescript/return-await` on Promise-returning functions outside try/catch. With the default `in-try-catch` mode, autofixers chase each other: `promise-function-async` adds `async`, `require-await` then demands an `await`, and `return-await` removes any `return await` outside a try/catch — leaving no resolvable state. The `"always"` mode keeps `return await` everywhere, breaking the cycle while preserving consistent stack traces.

---

# ultracite@7.6.5
Source: https://www.ultracite.ai/changelog/ultracite-7-6-5

## Patch Changes

-   3e08c25: Fix `ultracite init` failing with `npm error No workspaces found!` in npm monorepos. When `isMonorepo()` was true, nypm was passed `workspace: true`, which translates to `--workspaces` for npm — that installs in every workspace package and errors when patterns match nothing. We now skip the workspace flag for npm (the default root install is what we want) while preserving the flag for pnpm (`--workspace-root`) and yarn classic (`-W`). Applies to ultracite, husky, lefthook, and lint-staged installs.

---

# ultracite@7.7.0
Source: https://www.ultracite.ai/changelog/ultracite-7-7-0

## Minor Changes

-   24b0d27: Wire up the `nestjs` ESLint preset to actually enforce rules. Previously the preset exported an empty `const config = []`, meaning users who imported `ultracite/eslint/nestjs` got nothing. It now layers `@darraghor/eslint-plugin-nestjs-typed` (22 rules covering NestJS conventions, dependency injection correctness, and class-validator/Swagger usage) using the same dynamic-enable pattern as the other framework presets.

    Consumers who already had the empty preset in their config may see new violations on first run.

## Patch Changes

-   161418a: Add missing Biome stable rules to the core config:

    -   `suspicious/noDuplicateDependencies` → `"error"` — flags a dependency listed multiple times in the same group, or across `dependencies` and `devDependencies`, in `package.json`.
    -   `suspicious/useDeprecatedDate` → `"off"` — GraphQL-only convention requiring a `deletionDate` argument on `@deprecated`; too opinionated for the default preset.

-   9a2b548: Pin `@angular-eslint/eslint-plugin` to `^21.3.1` in `packages/cli/package.json`. Previously declared as `"latest"`, which defeats lockfile reproducibility and means each `bun install` could pull a newer version than what was tested at publish time. The current resolved version (21.3.1) is unchanged.

-   44f6d7f: Align ESLint presets with the oxlint configs (the maintained source of truth). Mostly tightens ESLint where oxlint was stricter; a few documented behavioural exceptions oxlint carries (rule conflicts, bun:test compat) are mirrored back.

    **core** — `eslint.mjs` now enforces `complexity`, `no-unused-private-class-members`, `sort-keys`, `sort-vars`, and full `prefer-destructuring` (object + array). `typescript.mjs` now enforces `no-confusing-void-expression`, `no-misused-promises`, `prefer-readonly`, `strict-boolean-expressions`, and sets `return-await: ["error", "always"]`. `import.mjs` now sets `consistent-type-specifier-style: ["error", "prefer-top-level"]`.

    **next** — added `next-env.d.ts` override that disables `import-x/no-unassigned-import` on the generated file.

    **remix** — added `routeTree.gen.ts` override that disables `unicorn/filename-case` and `unicorn/no-abusive-eslint-disable` on the generated file.

    **react** — disabled `react/jsx-boolean-value`, `react/no-unknown-property`, and `react/only-export-components` to match oxlint.

    **jest** — broadened test globs to `**/*.{test,spec}.{ts,tsx,js,jsx}` + `**/__tests__/**/*.{ts,tsx,js,jsx}` (previously missed `*.spec.*` and `__tests__/`). Disabled `no-empty-function` and `promise/prefer-await-to-then` in test scope. Disabled `jest/require-hook`, `jest/no-conditional-in-test`, `jest/no-hooks`, `jest/prefer-expect-assertions` to mirror oxlint's bun:test/mocking accommodations.

    **vitest** — same test-glob broadening; same `no-empty-function` / `promise/prefer-await-to-then` test-scope disables. Removed the `prefer-importing-vitest-globals` and `prefer-to-have-been-called-times` disables (oxlint enforces these). Added `prefer-lowercase-title: off` and `valid-title: off` to resolve the documented conflict with `prefer-describe-function-title` (#665).

-   63f6a18: Drop the redundant `react-hooks/exhaustive-deps: "error"` override in `config/eslint/react/rules/react-hooks.mjs`. The dynamic-enable pattern already sets every non-deprecated `react-hooks/*` rule to `"error"`, so the override was dead code. No behavior change.

-   5a0ce67: Refresh the misleading header comment in `config/eslint/core/rules/eslint-typescript.mjs`. The disables for the formatting rules (`brace-style`, `comma-dangle`, `indent`, etc.) used to defer to `@typescript-eslint`'s typed equivalents, but those rules were removed in v8. They're now disabled because Prettier/Oxfmt owns formatting. Updated the comment to reflect the actual rationale.

-   d681f70: Clean up `config/eslint/core/rules/typescript.mjs`: remove 22 stale overrides that referenced rules no longer present in `@typescript-eslint/eslint-plugin` v8.

    Most were formatting rules moved out to `@stylistic` (`block-spacing`, `brace-style`, `comma-dangle`, `comma-spacing`, `func-call-spacing`, `indent`, `key-spacing`, `keyword-spacing`, `lines-around-comment`, `lines-between-class-members`, `member-delimiter-style`, `no-extra-parens`, `object-curly-spacing`, `padding-line-between-statements`, `quotes`, `semi`, `space-before-blocks`, `space-before-function-paren`, `space-infix-ops`, `type-annotation-spacing`). The remaining two (`no-type-alias`, `sort-type-union-intersection-members`) were removed/deprecated upstream. All were dead no-ops — no behavior change.

---

# ultracite@7.8.0
Source: https://www.ultracite.ai/changelog/ultracite-7-8-0

## Minor Changes

-   4e2fea0: Add a dedicated `tanstack` framework preset for Biome, ESLint, and Oxlint. The ESLint preset layers `@tanstack/eslint-plugin-query`, `@tanstack/eslint-plugin-router`, and `@tanstack/eslint-plugin-start`, while the Biome and Oxlint presets relax file-naming conventions for `routes/` directories and the generated `routeTree.gen.ts`. Framework detection now maps `@tanstack/react-query`, `@tanstack/react-router`, and `@tanstack/react-start` to the new `tanstack` preset.

    Two behavior changes for existing consumers: TanStack Query rules now live in the `tanstack` preset instead of `react`, so projects that relied on Query rules must opt into `tanstack`; and TanStack Router projects now resolve to the `tanstack` preset rather than `remix`.

## Patch Changes

-   51a2af0: Recognize `.biome.json` and `.biome.jsonc` as valid Biome config files across the CLI. `detectLinter`, the `doctor` command, and the Biome config resolver now match the dot-prefixed names alongside `biome.json`/`biome.jsonc`, following Biome's [documented configuration file resolution order](https://biomejs.dev/guides/configure-biome/#configuration-file-resolution). Closes #700.

-   14b557c: Harden the generated standalone Husky hook by using `git add -- "$file"` when restaging formatted files. This prevents option-shaped filenames from being interpreted as Git options during the hook.

-   baa3dd0: Add `ignorePatterns` to the generated oxlint config at the root level so they are actually applied. Oxlint does not merge `ignorePatterns` through `extends` (see oxc-project/oxc#10223), so patterns set in the core preset were silently ignored. The generated config now sets `ignorePatterns: core.ignorePatterns` at the top level, reusing the patterns from the imported core preset.

-   bd27fd4: Add newly supported Oxlint rules from the latest release to the core, React, and Vitest presets:

    -   Core: `id-match`, `no-implicit-globals`, `no-implied-eval`, `prefer-arrow-callback`, `prefer-regex-literals`, `import/newline-after-import`, `jsdoc/require-throws-description`, `jsdoc/require-throws-type`, and `jsdoc/require-yields-type`
    -   React: `jsx-a11y/control-has-associated-label`, `jsx-a11y/no-interactive-element-to-noninteractive-role`, `jsx-a11y/no-noninteractive-element-interactions`, `jsx-a11y/no-noninteractive-element-to-interactive-role`, `react/no-object-type-as-default-prop`, and `react/no-unstable-nested-components`
    -   Vitest: `vitest/padding-around-after-all-blocks`

-   14b557c: Reject symlinked generated config targets before writing project files. CLI config writers now route through a shared project-file write guard that checks for symlinks and project-root escapes before mutating files.

-   14b557c: Validate package-manager names before generating agent and editor hook commands. Hook configuration now only uses supported package-manager prefixes, preventing unsafe values from being persisted into later-executed hook commands.

-   14b557c: Reject unsupported package-manager names during `ultracite init`. Explicit `--pm` values and detected `packageManager` metadata are now runtime-validated against the supported package managers before dependency installation, preventing malicious project metadata from selecting an arbitrary executable.

---

# ultracite@7.8.1
Source: https://www.ultracite.ai/changelog/ultracite-7-8-1

## Patch Changes

-   8335be7: Build the CLI with `bun build` and a `tsgo` type-check gate instead of tsup.
-   f747449: Fix the Oxlint TanStack preset so route files under `routes/` and `app/routes/` are exempt from `unicorn/filename-case`, matching the documented 7.8.0 behavior.
-   092597e: Fix generated `oxlint.config.ts` to be pre-formatted according to oxfmt rules, so `ultracite check` passes immediately after `ultracite init` without requiring a separate format step.
-   81da6e8: Generate agent and editor hook commands through nypm's package-manager script helper.
-   81da6e8: Keep hyphen-prefixed file operands from being forwarded to linters as options.

---

# ultracite@7.8.2
Source: https://www.ultracite.ai/changelog/ultracite-7-8-2

## Patch Changes

- 30971a8: Enable newly available Oxlint and Stylelint rules in the shared configs.

  For Oxlint, the core preset now enables `eslint/prefer-named-capture-group`,
  `jsdoc/require-yields-description`, `node/callback-return`,
  `typescript/method-signature-style`, and `unicorn/import-style`.

  The Vue preset now enables `vue/component-definition-name-casing`,
  `vue/no-computed-properties-in-data`, `vue/no-deprecated-props-default-this`,
  `vue/no-expose-after-await`, `vue/no-reserved-component-names`,
  `vue/no-shared-component-data`, `vue/no-watch-after-await`,
  `vue/require-prop-type-constructor`, `vue/require-render-return`,
  `vue/require-slots-as-functions`, `vue/return-in-emits-validator`,
  `vue/valid-define-options`, and `vue/valid-next-tick`.

  The Stylelint preset now enables `display-notation` with the `short` option.

---

# ultracite@7.8.3
Source: https://www.ultracite.ai/changelog/ultracite-7-8-3

## Patch Changes

- c863d09: Fix automatic editor extension installation during `ultracite init`.

  The whole command line (e.g. `code --install-extension`) was passed to
  `spawnSync` as the executable name, which always failed with `ENOENT` and
  silently fell back to the "install manually" message. The command is now split
  into the binary and its arguments, so the linter extension actually installs
  for VS Code-based editors.

- 6888129: Enable the `eslint/no-await-in-loop` rule as an error in the core Oxlint
  preset.

  Awaiting inside a loop forces each iteration to run sequentially, which can
  lead to serious performance issues when the asynchronous operations could
  otherwise run concurrently. Promoting this rule to an error encourages
  collecting promises and resolving them together (e.g. with `Promise.all`)
  instead of blocking on each one in turn.

- 62a9b5c: Fix the generated Husky pre-commit hook's error handling and section
  replacement.

  The standalone hook script set `set -e` and then tried to capture the
  formatter's exit code, re-stage files, and print a failure message — but a
  non-zero formatter exit terminated the script immediately, so none of that
  ever ran. The script now captures the exit code with `|| FORMAT_EXIT_CODE=$?`
  so files are re-staged and failures are reported with the right exit code.

  Re-running `ultracite init` also deleted everything from the `# ultracite`
  marker to the end of the hook, including commands the user added after the
  ultracite section. The section is now terminated with an explicit
  `# ultracite end` marker and updates replace only the section between the
  markers (legacy sections without an end marker are detected by their closing
  echo line).

- 6608ceb: Make the lint-staged integration idempotent and respect dedicated config
  files.

  `package.json` was always treated as the lint-staged config because the file
  exists in every project, so `ultracite init` wrote the lint-staged config into
  `package.json` even when a dedicated `.lintstagedrc.*` or
  `lint-staged.config.*` file was present — leaving two conflicting configs.
  `package.json` now only counts when it actually has a `lint-staged` key;
  otherwise the dedicated config file is updated (or `.lintstagedrc.json` is
  created).

  Re-running `ultracite init` also appended another `npx ultracite fix` entry on
  every run because the merge concatenates arrays. Updates are now skipped when
  the existing config already references ultracite.

- 4e847f7: Insert `--` before script arguments in npm hook commands.

  The post-edit hook command generated for npm projects was
  `npm run fix --skip=correctness/noUnusedImports`, where npm consumes the
  `--skip` flag itself instead of forwarding it to the script — so agent hooks
  ran a plain `ultracite fix`, including the unused-import removal the flag
  exists to prevent mid-edit. The generated command is now
  `npm run fix -- --skip=correctness/noUnusedImports`, matching the documented
  form.

- ecb0d5b: Scope the Stylelint step of `ultracite check` and `ultracite fix` (ESLint mode)
  to style files.

  Stylelint was previously given the same targets as ESLint and Prettier (or `.`
  when no files were passed), so it tried to parse `.ts`/`.json` files as CSS and
  failed with `CssSyntaxError`. Style files now pass through unchanged, directory
  targets become `**/*.{css,scss,sass,less}` globs, other files are dropped, and
  the step is skipped entirely when no style targets remain.
  `--allow-empty-input` is passed so projects without CSS still succeed.

- 61ea0a1: Fix the project-path write guard's error message and ordering.

  The "Refusing to write through directory outside project" error interpolated
  the `node:path` module instead of the offending file path, printing
  `[object Object]`. It now reports the actual path.

  `writeProjectFile` also created directories (`mkdir -p`) before running the
  path-escape check, so directories could be created outside the project before
  the guard threw. Validation now happens first; the parent-directory check
  resolves the nearest existing ancestor so writes into not-yet-created nested
  directories still work.

---

# ultracite@7.8.4
Source: https://www.ultracite.ai/changelog/ultracite-7-8-4

## Patch Changes

- e4ddd22: Ignore `.yarn` directories by default
- a1d5c06: Configure Oxfmt to never wrap prose (`proseWrap: "never"`)
- df709a4: Ignore `.wrangler` and `.wrangler-dry-run` output directories by default

---

# ultracite@7.9.0
Source: https://www.ultracite.ai/changelog/ultracite-7-9-0

## Minor Changes

- aea7fc0: Update Biome to 2.5.2 and enable the newly-stabilized rules. This adds coverage for the rules promoted out of nursery in Biome 2.5.0, including `noShadow`, `noUnnecessaryConditions`, `noUnusedInstantiation` (formerly `noFloatingClasses`), `useArrayFind`, `useDestructuring`, `useGlobalThis`, `useErrorCause`, `noNestedPromises`, GraphQL validation rules, and the recommended Vue/Next.js domain rules.
- 2687cf9: Align the ESLint and Biome presets with the oxlint preset, which is now the benchmark for rule decisions across linters. ESLint: rules that oxlint deliberately disables are now off (`no-console`, `no-continue`, `id-length`, `new-cap`, `max-depth`, `no-implicit-coercion`, `no-underscore-dangle`, `init-declarations`, `n/no-sync`, `promise/always-return`, `promise/catch-or-return`, `import-x/no-commonjs`, `import-x/no-dynamic-require`, `import-x/no-nodejs-modules`, `import-x/unambiguous`, `import-x/no-anonymous-default-export`, `@typescript-eslint/explicit-member-accessibility`, `@typescript-eslint/explicit-module-boundary-types`, `@typescript-eslint/no-require-imports`, and the `unicorn` rules `explicit-length-check`, `max-nested-calls`, `no-process-exit`, `prefer-global-this`, `prefer-string-raw`, `prefer-top-level-await`); `consistent-type-definitions` now enforces `interface` instead of `type`, matching oxlint and Biome; `no-void` allows statement position to coexist with `no-floating-promises`; `import-x/no-named-as-default` is enabled; and `curly` and `no-unexpected-multiline` are re-enabled past `eslint-config-prettier`. Biome: `noAwaitInLoops` and `noIncrementDecrement` are now errors and the `useSortedKeys` assist is on (matching `no-await-in-loop`, `no-plusplus`, and `sort-keys` in the other presets), while `useGlobalThis` is off (matching `unicorn/prefer-global-this`).
- 73c1993: Require ESLint 10 for ESLint setups. The plugin suite upgrade (notably `eslint-plugin-unicorn` 70 and `eslint-plugin-astro` 2) requires ESLint 10, but `ultracite init` still installed `eslint@^9.0.0`, which crashed at config load time. Init now installs `eslint@^10.0.0` and `@eslint/js@^10.0.0`, and the presets are fixed for ESLint 10 compatibility: `settings.react.version` is pinned to `19.0.0` instead of `"detect"` (detection uses an API removed in ESLint 10), `react/jsx-filename-extension` and `react/forward-ref-uses-ref` are disabled (their implementations use removed APIs; the former is already off in the oxlint preset and the latter is covered by `react-doctor/no-react19-deprecated-apis`), the react config re-applies `eslint-config-prettier` so JSX formatting rules stay off (several crash under ESLint 10), and `import-x/no-unused-modules` is disabled (it is a warning-emitting no-op under ESLint 10). Note that some plugins (`eslint-plugin-github`, `eslint-plugin-react`, `eslint-plugin-jsx-a11y`, `eslint-plugin-solid`, `@tanstack/eslint-plugin-start`) have not yet updated their declared peer ranges to include ESLint 10 even though they work at runtime, so strict package managers may report peer dependency warnings.
- 4cfdf3d: Add `eslint-plugin-jsdoc` to the ESLint preset. The oxlint preset already enforces a set of jsdoc rules, but the ESLint preset had no jsdoc coverage at all. The plugin is now installed by `ultracite init` for ESLint setups and enables the same rule selection the oxlint preset enforces (`check-access`, `check-property-names`, `check-tag-names`, `empty-tags`, `implements-on-classes`, `no-defaults`, and the `require-*` description/name/type rules), keeping the two presets in lockstep.
- 0b8fc12: Upgrade the ESLint plugin suite and enable the new rules that ship with it. Notable bumps: `eslint-plugin-unicorn` 64 → 70 (adds a large batch of new correctness and quality rules), `eslint-plugin-astro` 1 → 2 (adds `no-omitted-end-tags`, now requires ESLint 10), `eslint-plugin-sonarjs` 4.0 → 4.1 (adds test-assertion and ReDoS rules like `super-linear-regex`), `eslint-plugin-svelte` 3.19 → 3.20 (adds `no-at-const-tags`), plus `@typescript-eslint`, `eslint-plugin-import-x`, `eslint-plugin-n`, `@vitest/eslint-plugin`, and others. Two Unicorn rules that were renamed are re-mapped in the config (`prefer-dom-node-dataset` → `dom-node-dataset`, `prevent-abbreviations` → `name-replacements`). Two new Unicorn rules are disabled: `prefer-temporal` (since `Temporal` still lacks broad runtime support) and `no-asterisk-prefix-in-documentation-comments` (it fights the conventional JSDoc comment style).
- 4440393: Bring the oxlint preset closer to ESLint parity with two new presets that run ESLint plugins through oxlint's JS plugin support: `ultracite/oxlint/github` (eslint-plugin-github) and `ultracite/oxlint/sonarjs` (eslint-plugin-sonarjs, 187 rules — type-aware rules are excluded since the JS plugin bridge provides no type information, and `no-reference-error` is off because the bridge provides no globals). `ultracite init` now adds both presets to generated oxlint configs and installs the two plugins; existing configs are untouched until the next `init`, and either preset can be dropped from `extends` to opt out (the plugins add roughly 1–3s to a lint run for the JS runtime bridge). Rule decisions mirror the oxlint benchmark in both directions: the ESLint preset now disables `sonarjs/file-header` (it errored on every file), `sonarjs/arrow-function-convention` (fights the formatter), `sonarjs/cyclomatic-complexity`, `sonarjs/max-lines`, `sonarjs/max-lines-per-function`, `sonarjs/nested-control-flow` (duplicates of core rules the preset disables), `sonarjs/shorthand-property-grouping` (conflicts with `sort-keys`), and `github/no-dataset` (conflicts with `unicorn/prefer-dom-node-dataset`), and sets `sonarjs/cognitive-complexity` to 20 to match Biome's `noExcessiveCognitiveComplexity`. Switching linters with `init` no longer removes dependencies that the newly selected linter still needs.
- f7025b1: Extend cross-linter parity to the framework presets and add an automated parity check. The oxlint react preset now explicitly lists all 102 non-nursery react/react-perf/jsx-a11y rules (previously only ~20 were configured, so most a11y and correctness rules silently never ran) and the next preset lists all 21 nextjs rules, with decisions matching the ESLint presets. The revived exhaustiveness test (the `oxlint --rules` markdown output it parsed is empty as of oxlint 1.72, so it was passing vacuously) also caught five newly stabilized rules which are now enabled: `getter-return`, `no-unreachable`, `oxc/branches-sharing-code`, `unicorn/prefer-export-from`, and `unicorn/prefer-single-call`. ESLint preset fixes that fell out of the audit: `no-loss-of-precision` and `no-duplicate-imports` are re-enabled for TypeScript files (their `@typescript-eslint` twins were removed in v8, leaving TS uncovered), `no-duplicate-imports` gets `allowSeparateTypeImports` to match oxlint, the react/vue configs now only re-apply the `react/`-`vue/`-prefixed entries of `eslint-config-prettier` so they can't clobber unrelated rules, the svelte preset keeps the formatting rules disabled that `eslint-plugin-svelte`'s own prettier preset lists, and `astro/semi` is off (Prettier owns formatting). A new `compare-rule-parity` script runs as part of `validate:configs`: it resolves the effective ESLint rule sets with ESLint's own config resolution, normalizes names to oxlint's, and fails on any divergence not recorded in an explicit allowlist — currently just two entries (`sonarjs/no-reference-error`, `unicorn/number-literal-case`), both with documented reasons.
- 223233f: Add [React Doctor](https://www.react.doctor) rules to the ESLint and Oxlint React, Next.js, and TanStack presets. This enables React Doctor's own rules — the "You Might Not Need an Effect" family (`no-fetch-in-effect`, `no-derived-state`, `no-mirror-prop-effect`, etc.) plus its render-performance, hydration, server-component, security, and framework-specific rules — via `eslint-plugin-react-doctor` and the `oxlint-plugin-react-doctor` JS plugin. Rules that React Doctor ports from `eslint-plugin-react`, `eslint-plugin-react-hooks`, and `eslint-plugin-jsx-a11y` are intentionally left off to avoid duplicate diagnostics with the plugins Ultracite already ships.

## Patch Changes

- d247ff2: Migrate stale linter and formatter configuration when switching toolchains during init. Running `ultracite init` now removes config files and dependencies for unselected Biome, ESLint/Prettier/Stylelint, or Oxlint/Oxfmt setups before writing the selected toolchain config.
- e24068b: Sort `package.json` keys when using Biome

---

# ultracite@7.9.1
Source: https://www.ultracite.ai/changelog/ultracite-7-9-1

## Patch Changes

- ecd10cc: Disable `sonarjs/no-implicit-dependencies` and `github/no-implicit-buggy-globals` in the oxlint and ESLint presets. Both produce false positives through oxlint's JS plugin bridge: `no-implicit-dependencies` has no dependency-manifest resolution so it flags builtin (`bun:test`) and workspace imports as missing dependencies, and `no-implicit-buggy-globals` misreads module-scoped declarations such as Astro frontmatter as implicit globals.
- c76f59d: Disable `sonarjs/file-name-differ-from-class` in the oxlint and ESLint presets. It fires on any file whose name differs from an exported class, which is noise for the many config and module files that export objects rather than classes.
- 29e30ce: Fold the github and sonarjs rules into the oxlint core preset. The standalone `ultracite/oxlint/github` and `ultracite/oxlint/sonarjs` presets are removed — ultracite ships framework presets, not individual plugins. Their rules now live in `ultracite/oxlint/core`, so every oxlint setup gets eslint-plugin-github and eslint-plugin-sonarjs through oxlint's JS plugin bridge, matching how the ESLint preset already bundles them into core.

  This is a breaking change to generated configs: `ultracite/oxlint/github` and `ultracite/oxlint/sonarjs` no longer exist. Re-run `ultracite init` to regenerate `oxlint.config.ts`.

  Also fixed: nine sonarjs rules (`async-test-assertions`, `hooks-before-test-cases`, `no-duplicate-test-title`, `no-empty-test-title`, `no-floating-point-equality`, `no-forced-browser-interaction`, `no-trivial-assertions`, `prefer-specific-assertions`, `super-linear-regex`) that exist in eslint-plugin-sonarjs but that oxlint's JS plugin bridge does not register. Naming them made oxlint hard-fail config parsing, which broke `ultracite fix`/`check` for oxlint projects using the sonarjs preset. They are omitted from oxlint core (still enabled in the ESLint preset), and a test now runs oxlint against core to catch this class of regression.

  The React Doctor, github, and sonarjs plugins are installed into your project's devDependencies at init (as the ESLint plugins already were), rather than bundled as dependencies of ultracite — oxlint resolves JS plugin specifiers from the project root, so they must be installed there directly.

- 8a4291f: Upgrade to Oxlint 1.72.0 and Oxfmt 0.57.0. Oxfmt 0.57 adds native CSS and GraphQL formatters. The five new non-nursery Oxlint rules from the 1.71/1.72 releases are already covered by the presets (`node/no-sync`, `node/no-mixed-requires`, `unicorn/prefer-number-coercion`, `unicorn/max-nested-calls`, `vue/no-async-in-computed-properties`). The markdown `:::` container-directive fence patch (which keeps `proseWrap: "never"` from folding fences into prose) was regenerated against the 0.57 bundle.

---

# ultracite@7.9.2
Source: https://www.ultracite.ai/changelog/ultracite-7-9-2

## Patch Changes

- c335a1f: Add `**/node_modules` and `**/.git` to the shared ignore patterns. oxlint only skips `node_modules` when a `.gitignore` lists it, so in projects without one, `ultracite fix` would lint and autofix files inside `node_modules` — corrupting installed packages (e.g. rewriting `var` enum wrappers in `typescript/lib/typescript.js` to self-referencing `const`, causing "Cannot access 'Comparison' before initialization" when oxlint loads eslint-plugin-sonarjs). Fixes #737.

---

# ultracite@7.9.3
Source: https://www.ultracite.ai/changelog/ultracite-7-9-3

## Patch Changes

- dc6d760: Disable the `n/no-unpublished-import` rule in the ESLint core config. This rule flags imports of packages that aren't listed as published dependencies, but it produces a lot of false positives in practice, so it's now turned off.
- 15ecfba: Fix `ultracite init --linter eslint` installing an unusable toolchain. The generated ESLint config imports `eslint-plugin-storybook` unconditionally (which requires the `storybook` peer) and the generated Stylelint config extends `stylelint-config-standard` / `stylelint-config-idiomatic-order` / `stylelint-prettier`, but none of those packages were installed — so a fresh ESLint setup failed to load with "Cannot find package 'storybook'" or "Could not find stylelint-config-standard". These four packages are now installed with the ESLint linter.
- 2f73a41: Upgrade to oxlint 1.73.0 and oxfmt 0.58.0, and enable the new lint rules they introduce: `no-unreachable-loop`, `unicorn/explicit-timer-delay`, and `unicorn/no-confusing-array-with`.
- 83b2783: Add an `[astro]` formatter mapping (`astro-build.astro-vscode`) to the oxlint VS Code editor settings generated by `ultracite init`, since oxfmt doesn't format `.astro` files.
- d186c53: Move every JS-plugin-based rule set out of the Oxlint core and framework presets and into a single opt-in `ultracite/oxlint/js-plugins` preset. This covers `eslint-plugin-github` and `eslint-plugin-sonarjs` (previously in core) as well as `oxlint-plugin-react-doctor` (previously bundled into the `react`, `next`, and `tanstack` presets). The core, `react`, `next`, and `tanstack` presets now run entirely on Oxlint's native Rust rules, so new setups no longer install those dependencies and no longer pay the slower JS-plugin lint pass. To keep the extra ESLint-parity and React Doctor rules, install `eslint-plugin-github`, `eslint-plugin-sonarjs`, and `oxlint-plugin-react-doctor` and extend `ultracite/oxlint/js-plugins` alongside `core` (and your framework preset).
- 057753e: Add performance benchmarks for `ultracite check` / `ultracite fix` across all three providers (oxlint, biome, eslint). A new CI job builds the PR and its base branch on the same runner, benchmarks them interleaved, and fails on a statistically significant regression (median ratio > 1.25x with Mann-Whitney U p < 0.05) so config changes can't silently slow the linters down again.

---

# ultracite@7.9.4
Source: https://www.ultracite.ai/changelog/ultracite-7-9-4

## Patch Changes

- f480c12: Upgrade Biome to 2.5.3 to fix the LSP scanner deadlock ([#10845](https://github.com/biomejs/biome/issues/10845)) where editors get stuck on "Biome is scanning the project".
- 1d70c40: Fail fast with an actionable message when Biome can't resolve `ultracite/biome/core`. Biome resolves that config out of the project's `node_modules`, so it errors with an opaque "module not found" whenever Ultracite isn't installed there — a state `npx ultracite check` / `bunx ultracite check` hide, because they run the CLI from a temp cache regardless. `check` and `fix` now detect it before invoking Biome and say what's actually wrong, and `doctor` verifies that Ultracite resolves rather than just appearing in `package.json` ([#750](https://github.com/haydenbleasel/ultracite/issues/750)).
- 38d10bc: Move Biome's `noUnknownAttribute` rule out of the core preset and into the `react` preset. The rule only recognises React's JSX attribute names, so projects using Solid, Svelte, Vue, or Qwik were incorrectly flagged for framework-standard attributes such as `class`.
- cf723bd: Add interactive and non-interactive selection for optional Oxlint JS plugins during init.

---

# ultracite@8.0.0
Source: https://www.ultracite.ai/changelog/ultracite-8-0-0

## Major Changes

- d0875c0: Every agent now reads Ultracite's rules from `AGENTS.md`. `init` writes the rules there once, whichever agents you pick, and only adds a file for the four agents that need one more step to see them:
  
  - **Claude Code** reads `AGENTS.md` only when the project has no `CLAUDE.md`, so `init` adds an `@AGENTS.md` import to the project's `CLAUDE.md` or `.claude/CLAUDE.md` when there is one.
  - **Gemini CLI** reads `GEMINI.md` by default, so `init` adds `AGENTS.md` to `context.fileName` in `.gemini/settings.json`, keeping `GEMINI.md`.
  - **Aider** gets `.aider.conf.yml` pointed at `AGENTS.md`, as before.
  - **Replit Agent** reads only `replit.md`, so it keeps a copy of the rules there.
  
  Firebender now reads `AGENTS.md` too. The `init` prompt asks which agents you use and lists `AGENTS.md` (Universal) plus those four.
  
  Projects set up by earlier versions move over the next time `init` runs: it takes Ultracite's block out of `.claude/CLAUDE.md`, `GEMINI.md`, `.firebender/rules/ultracite.mdc` and Aider's `ultracite.md`, removes a file left with nothing else in it, and adds the import or settings that agent needs. That happens whenever one of those files still holds the rules, whichever agents you pick, since a leftover `.claude/CLAUDE.md` stops Claude Code from reading `AGENTS.md`.
  
  A `CLAUDE.md`, `GEMINI.md` or `replit.md` that is a symbolic link to `AGENTS.md`, or that `AGENTS.md` links to, already gives that agent the rules, so `init` leaves it as it is. `init` never writes through or removes a symbolic link to another file; it prints what to add to that file instead.
- 3ee5b8c: Aider now loads Ultracite's rules and lints each file it edits. Aider reads no instructions file on its own, so the `ultracite.md` that `init --agents aider` used to write was never loaded. Now `init` writes the rules to `AGENTS.md` and merges two keys into `.aider.conf.yml`: `read: AGENTS.md`, and `lint-cmd` set to the project's `ultracite fix`, which Aider runs on every file it edits, asking the model to fix whatever is left. The rest of the file, comments included, stays as written, a `lint-cmd` that runs another linter is left alone, and an `ultracite.md` that holds nothing but the rules is removed. Aider keeps its own option in the `init` prompt, since the universal `AGENTS.md` option doesn't write `.aider.conf.yml`.
  
  The agent list also uses the current names for Deep Agents, goose and Gemini CLI. Their `--agents` IDs don't change.
- f4c8a32: Make every rule in the Biome core preset an error. `noSuspiciousSemicolonInJsx` came from Biome's recommended set at warning level, so `ultracite check` passed with it unless the React preset was on. It and the two other rules core inherited from that set, `noDuplicateJsxProps` and `noVoidElementsWithChildren`, are now set to `error` explicitly.
- ed5ed04: `compat/compat` is now an error in the ESLint core preset. It was the last warning-level rule in any preset, so `ultracite check` passed while it reported browser APIs your [browserslist](https://github.com/browserslist/browserslist) targets don't support. Set your targets in a `browserslist` key in `package.json` or a `.browserslistrc` file, or turn the rule off in your config if the project only runs on a server.
  
  A project that sets no targets is now checked against [Baseline Widely available](https://web.dev/baseline) browsers (`baseline widely available`). eslint-plugin-compat used browserslist's `defaults` there, which include Opera Mini and Chrome 109, so `fetch`, `URL` and `Array#toSorted()` failed in almost every project. Ultracite only sets these targets when it finds no browserslist config from the directory ESLint runs in and no `BROWSERSLIST` environment variable, since the plugin would add them to your own targets rather than replace them. In a monorepo that sets targets only in its packages, add them at the root too, or set `settings.browsers` yourself.
- 16fa476: Lint the scripts in Vue, Svelte and Astro components with the ESLint core rules. Core's globs only matched `.js` and `.ts` files, so a `.vue` file got only the Vue rules, a `.svelte` file only the Svelte rules, and an `.astro` file's frontmatter only the Astro rules, while Oxlint already runs its core rules on those scripts. The `vue`, `svelte` and `astro` presets now apply core's rules to their components, including the TypeScript rules, with the type-checked ones off because a script block isn't part of a tsconfig.
  
  - Components now get core's filename rule like any other file, as on Oxlint, so a PascalCase component such as `TaskList.vue` is reported. SvelteKit route files (`+page.svelte`) are exempt, and Astro and Nuxt pages (`[slug].astro`, `[id].vue`) get the same route-aware pattern as other `pages/` files, on ESLint and in Oxlint's JS plugins.
  - In Svelte components and rune modules, `prefer-const`, `unicorn/no-top-level-assignment-in-function` and `sonarjs/declarations-in-global-scope` are off: `svelte/prefer-const` replaces the first, and the other two misread `$props()` and `$state` in a component's scope. SvelteKit's `PageProps` and `LayoutProps`, and Astro's `Props`, are allowed by `unicorn/name-replacements`.
- ed5ed04: Cypress and Storybook rules move out of the ESLint core preset into opt-in framework presets, `ultracite/eslint/cypress` and `ultracite/eslint/storybook`. Core loaded both plugins for every project, so `init` installed `eslint-plugin-cypress`, `eslint-plugin-storybook` and the whole `storybook` package for every ESLint setup, whether or not the project used them.
  
  `init` now offers `cypress` and `storybook` with the other frameworks (`--frameworks cypress storybook`). It preselects them when `cypress` or `storybook` is in `package.json`, and installs their plugins only when you pick them. To keep linting Cypress specs and stories, add the presets to `eslint.config.mjs` after `core`:
  
  ```js
  import core from "ultracite/eslint/core";
  import cypress from "ultracite/eslint/cypress";
  import storybook from "ultracite/eslint/storybook";
  
  export default [...core, ...cypress, ...storybook];
  ```
  
  Oxlint and Biome have no Cypress or Storybook rules, so `ultracite/oxlint/cypress`, `ultracite/oxlint/storybook`, `ultracite/biome/cypress` and `ultracite/biome/storybook` are empty presets that keep the framework selectable with every linter.
- ed5ed04: ESLint and Stylelint no longer run Prettier as a rule. `ultracite check` and `ultracite fix` already run Prettier as their own step, so the `prettier/prettier` rule from `eslint-plugin-prettier` and `stylelint-prettier` formatted and reported every file a second time. The ESLint core preset and the Stylelint preset drop those plugins and keep `eslint-config-prettier`, so no lint rule fights Prettier, and `init` no longer installs `eslint-plugin-prettier` or `stylelint-prettier`.
  
  ESLint and Stylelint now report only lint problems. Formatting problems come from the Prettier step of `ultracite check`, so running `eslint` or `stylelint` on their own no longer reports formatting. A config that sets `prettier/prettier` itself now fails with an unknown-rule error: remove that setting, or install the plugin and register it in your own config to keep it.
  
  Zed formats with Prettier on the ESLint toolchain. `init` used to set ESLint's language server as Zed's formatter for JavaScript, TypeScript and TSX, which only applied Prettier through the `prettier/prettier` rule, so in v8 Zed would have applied ESLint's fixes without formatting. It now keeps ESLint's fixes as code actions and sets `"formatter": "prettier"`, so Zed's Prettier integration formats afterwards with your project's Prettier config and plugins. Re-running `init` updates `.zed/settings.json`, and `ultracite upgrade --claude` or `--codex` makes the same change.
- ed5ed04: The ESLint rules that need type information are now opt-in, as they already are on Oxlint and Biome. The core preset no longer turns on the project service or the type-checked `@typescript-eslint` rules, such as `no-floating-promises`, `no-unsafe-return` and `strict-boolean-expressions`, so it lints TypeScript without a tsconfig and without building a TypeScript program, which is much faster. Where a type-checked rule replaced a core ESLint rule on TypeScript files (`no-implied-eval`, `no-throw-literal`, `prefer-destructuring`, `prefer-promise-reject-errors`, `require-await`), core now runs the ESLint rule, as Oxlint does without type information. The 37 SonarJS rules and one Unicorn rule that do nothing without type information, such as `sonarjs/deprecation`, `sonarjs/no-ignored-return` and `unicorn/no-non-function-verb-prefix`, move with them. SonarJS rules that use type information only when it's there, such as `sonarjs/no-small-switch` and its regular expression rules, stay in core.
  
  The type-checked rules live in a new `ultracite/eslint/type-aware` preset. Framework plugins with type-checked rules have an add-on after their preset: `ultracite/eslint/<framework>/type-aware` for `angular`, `jest`, `nestjs`, `qwik`, `tanstack` and `vitest`. `init --type-aware` adds the preset and the add-ons for the frameworks you pick, and re-running `init` without the flag keeps them. To keep type-aware linting, add them after `core` and after each framework:
  
  ```js
  import core from "ultracite/eslint/core";
  import typeAware from "ultracite/eslint/type-aware";
  import vitest from "ultracite/eslint/vitest";
  import vitestTypeAware from "ultracite/eslint/vitest/type-aware";
  
  export default [...core, ...typeAware, ...vitest, ...vitestTypeAware];
  ```
- 7965ec2: `ultracite fix --hook` now hands the problems it can't fix back to the agent. In Claude Code, CodeBuddy, Codex, Deep Agents, Grok Build and VS Code's Local agent (which runs the GitHub Copilot hook), the hook prints everything the linter and formatter report to stderr and exits with code 2 when problems remain, which those hosts show to the agent so it fixes them in its next step. Devin reads exit code 2 as "block", so under Devin the hook exits with 0 and passes the problems as `hookSpecificOutput.additionalContext` instead. Cursor and the Copilot CLI and cloud agent don't pass a hook's output to the agent, so their hooks keep the previous output and exit code.
- ed5ed04: `ultracite init` now asks before it changes files it doesn't own, and asks every question before it writes anything.
  
  - When you pick a linter other than the one the project uses, an interactive run lists the other linters' config files and packages and asks before removing them. If you keep them, init warns when `ultracite check` would still find and run the old linter. `--yes` removes them without asking, as before.
  - An ESLint setup keeps legacy `.eslintrc` files. ESLint 10 doesn't read them, so they can't conflict with the flat config, and `ultracite doctor` no longer flags them on an ESLint setup. Moving to Biome or Oxlint still removes them.
  - Init only turns on `strictNullChecks` in your `tsconfig*.json` files when type-aware linting is on, since only the type-aware rules need it, and an interactive run lists the files and asks first. It used to change every tsconfig on every run.
  - In a TypeScript project, an interactive run asks whether to turn on type-aware linting when `--type-aware` isn't passed. A project that already has it keeps it.
- ed5ed04: `ultracite init` has a `--yes` (`-y`) flag for running without prompts, and `--quiet` now only controls output.
  
  - `--yes` takes the default for every question no flag answers, without asking. Init does this on its own when `CI` is `true` or `1`, or when there's no terminal to answer prompts in, so it never waits for input in a pipeline.
  - `--quiet` leaves out the intro banner, spinners and progress messages, and no longer skips the prompts. A script that ran `init --quiet` to avoid them should pass `--yes --quiet`.
  - Warnings now print in quiet runs too, such as the one for a `check` or `fix` script that init left as it was because it runs another tool.
- cbb349c: Add three agents, and rename Windsurf to Devin Desktop.
  
  - `init --agents` now takes `fx` (Vercel Labs), `antigravity` (Antigravity CLI, Google's successor to Gemini CLI for consumer accounts) and `grok` (Grok Build). All three read `AGENTS.md`.
  - `init --hooks grok` writes a post-edit hook to `.grok/hooks/ultracite.json` in Claude Code's format. Grok Build runs it after each `Write` or `Edit` once you trust project hooks with `/hooks-trust`, and hands the problems `ultracite fix --hook` leaves back to the model. `fix --hook` now recognises Grok's own tool names (`search_replace`, `hashline_edit`), which it used to skip. Grok also reads `.claude/settings.json`, but runs a hook once when several files give it the same event, command and matcher, as the Claude Code and Grok Build hooks do, so a project can have both.
  - Windsurf is now Devin Desktop, with the editor and hook ID `devin` instead of `windsurf`, which init still accepts with a note to switch. Its hook now goes in `.devin/hooks.v1.json`, which Devin Local reads.
- ed5ed04: Ultracite now requires Node.js 22.18 or later, or Bun, and says so in its `engines` field. The CLI's dependencies have needed Node 22 since 7.10.0, so on Node 20 it stopped at startup with `TEXT_ENCODINGS.union is not a function`, and the `oxlint.config.ts` that `init` writes needs Node 22.18 to load on the Node 22 line. Node 20 reached end of life in April 2026.
  
  Requires Node.js >= 22.18.0
- ed5ed04: `ultracite init --type-aware` now turns on type-aware linting for Oxlint. It used to install `oxlint-tsgolint` without telling Oxlint to use it, so rules that need type information, such as `typescript/no-floating-promises`, only ran when you passed `--type-aware` to `ultracite check` yourself. Init now also sets `options: { typeAware: true }` in `oxlint.config.ts`, so `check`, `fix` and the editor extension run them. A config with an `options` object of its own is left as written, with a note to add `typeAware: true` to it. Re-running `init` on a project that has `oxlint-tsgolint` installed turns it on, which can report new problems.
- edc6ca6: Update the agents `ultracite init` sets up to match what's still shipping.
  
  - Remove Roo Code (shut down in May 2026), Continue (no longer maintained since Cursor acquired it), Firebase Studio (closing in March 2027) and MCPJam (an MCP testing tool rather than a coding agent). `--agents roo-code`, `continue`, `firebase-studio` and `mcpjam` now write the rules to `AGENTS.md`, as `universal` does, with a warning, and the skill installer no longer targets `.roo` or `.continue`. Files earlier versions wrote for them, such as `.roo/rules/ultracite.md`, are left in place.
  - Amazon Q CLI is now Kiro CLI, with the ID `kiro-cli` instead of `amazon-q-cli`, which init still accepts with a note to switch. Kiro reads `AGENTS.md` in both its CLI and IDE and ignores `.amazonq/rules` once a project has a `.kiro` folder, so init writes the rules to `AGENTS.md` (and `universal` covers it) instead of `.amazonq/rules/ultracite.md`.
  - Mux is now Xum, with the ID `xum` instead of `mux`, which init still accepts with a note to switch.
  - Kimi CLI is now Kimi Code CLI, with the ID `kimi-code` instead of `kimi-cli`, and Snowflake Cortex Code is now Snowflake CoCo, with the ID `snowflake-coco` instead of `snowflake-cortex`. The old IDs still work, with a note to switch. AMP is now Amp; its ID doesn't change.
- ed5ed04: The pre-commit hooks that `ultracite init` sets up now fix only the files you staged, instead of running `ultracite fix` on the whole project.
  
  - **Husky:** the hook passes the staged files to `ultracite fix` and re-stages them. A file you staged only part of is fixed but no longer re-staged, because `git add` would also have committed the changes you left unstaged. The hook lists those files so you can review the fixes and stage them yourself.
  - **Lefthook:** the job runs `ultracite fix {staged_files}`, so Lefthook passes the staged files that match its globs, and `stage_fixed` re-stages only those.
  - **pre-commit:** the hook no longer sets `pass_filenames: false`, so pre-commit passes the staged files to `ultracite fix`. It also sets `require_serial: true`, which keeps it to a single `ultracite fix` run.
  
  Since the globs now decide which files get fixed, the Lefthook job and the pre-commit hook match every file type the linters and formatters handle: `.js`, `.jsx`, `.mjs`, `.cjs`, `.ts`, `.tsx`, `.mts`, `.cts`, `.json`, `.jsonc`, `.css`, `.scss`, `.less`, `.vue`, `.svelte`, `.astro`, `.html`, `.md`, `.mdx`, `.yaml`, `.yml`, `.graphql` and `.gql`. Before, they matched only `.js`, `.jsx`, `.ts`, `.tsx`, `.json`, `.jsonc` and `.css`. The lint-staged glob, which already passed only the staged files that match it, now covers the same types too; it used to leave out `.mjs`, `.cjs`, `.mts`, `.cts`, `.less`, `.vue`, `.svelte`, `.astro`, `.html`, `.yaml`, `.yml`, `.graphql` and `.gql`, so those files were never fixed on commit. The pre-commit hook uses a `files` pattern instead of `types_or`, because pre-commit has no file type tags for `.jsonc`, `.mts`, `.cts` or `.gql`.
  
  Re-running `ultracite init` with the same integrations updates the hooks, globs and file types that earlier versions wrote, in place. Hooks, globs and types you wrote or edited yourself are left alone.
- ed5ed04: `ultracite init` and `upgrade` now install `oxlint`, `oxfmt` and `oxlint-tsgolint` within caret ranges of the versions the presets were checked against (`^1.86.0`, `^0.71.0` and `^7.0.2004`), instead of the latest release. Biome is still installed at the exact version. `oxfmt` is still before 1.0, so its caret range holds the minor version: a new `oxfmt` minor can no longer change how files are formatted the next time you run `upgrade`, and a new `oxlint` major can no longer fall outside the supported range. The `oxfmt` peer range is now `>=0.71.0 <1`, so `ultracite doctor` fails on an `oxfmt` older than 0.71.0 and warns on 1.0 or later.
  
  Requires oxfmt >= 0.71.0 and < 1.0.0
  
  Requires prettier >= 3.5.3 (the version `prettier-plugin-astro` needs)
- 528a17c: `ultracite upgrade` now brings your configuration up to date, not just your packages, and replaces the manual upgrade guides.
  
  - `--claude` and `--codex` hand the configuration changes a project still needs to that agent's CLI, after Ultracite and the toolchain are installed. The agent gets the upgrade guide for each major release the configuration predates: Biome 2's config format (v5), the per-framework presets (v6), the `ultracite/biome/*` preset paths and `check` and `fix` commands (v7), and this release's changes (v8): removing `prettier/prettier` from ESLint and Stylelint configs, importing the new Cypress, Storybook and type-aware ESLint presets where the project needs them, turning on Oxlint's `typeAware` when `oxlint-tsgolint` is installed, formatting with Prettier in Zed, and adding `--yes` to `init --quiet`. It runs as it does for `fix --claude`, limited to editing files, and Ultracite checks the project again afterwards, exiting non-zero when a change is still missing.
  - Which guides apply is decided from the project, not the version it came from, so a project that skipped a major release or had `ultracite` bumped by hand still gets them. Without an agent flag, `upgrade` lists them. They ship in the package under `skills/ultracite/references/upgrades/` and with the Ultracite skill.
  - `--version <version>` installs a given release, such as `7` (the newest 7.x) or `7.12.4`, instead of the latest. `--claude` and `--codex` need 8 or later, so `upgrade` stops before installing anything when they're passed with an earlier release.
  - When the package manager fails to install a package, `upgrade` and `init` print its output and how to retry instead of a stack trace, and for an npm peer dependency conflict (`ERESOLVE`) it suggests `legacy-peer-deps=true` in `.npmrc`.
  - Ultracite's own `-v` and `--version` now only work before a command, so `upgrade --version` is the upgrade's option. `ultracite --version` prints the version as before.

## Minor Changes

- 3883a3d: Add a post-edit hook for Codex. `init --hooks codex` writes `.codex/hooks.json` with a `PostToolUse` hook that runs `ultracite fix --hook` after each `apply_patch` edit, fixing just the files the patch adds, updates or moves. Codex loads the hook once you trust the project and review it in `/hooks`, and when the hook exits with code 2 it hands the problems `fix` couldn't settle to the model as the patch's result. See [Codex hooks](https://learn.chatgpt.com/docs/hooks).
- a30bde7: Add a post-edit hook for Deep Agents. `init --hooks deepagents` writes `.deepagents/hooks.json` in Claude Code's format, with a `PostToolUse` hook that runs `ultracite fix --hook` after each `Write` or `Edit`. Deep Agents Code (`dcode`) runs a project's hooks once you trust the workspace (headless runs need `--trust-project-hooks`), and when the hook exits with code 2 it appends the problems `fix` couldn't settle to the tool result the model reads.
- ed5ed04: `ultracite init --agents` no longer stops on an agent ID it doesn't know. Every agent reads the rules from `AGENTS.md`, so an unknown, retired or misspelled ID gets that file, as `universal` does, with a warning that lists the valid IDs. The old IDs of renamed agents and editors (`amazon-q-cli`, `mux`, `kimi-cli`, `snowflake-cortex` and `windsurf`) map to the new ones with a note to switch. `--editors` and `--hooks` still stop on an ID they don't know.

## Patch Changes

- ed5ed04: Agent hooks now run the project's installed Ultracite directly, as `npx ultracite fix --hook` (or `pnpm exec`, `bunx` and so on), instead of the project's `fix` script. Init leaves a `fix` script alone when the project already has one that runs another tool, and the hook then ran that tool with `--hook` added. Re-running `ultracite init --hooks` rewrites hooks from earlier versions in place.
- 3883a3d: `ultracite fix --hook` no longer fixes the whole project after an `apply_patch` edit that only deletes files. Such a patch leaves no file to fix, so the hook now does nothing, where it used to fall back to a whole-project run that could reformat files the agent never touched.
- 6bfeba2: Fix Biome refusing to run in a new project with no ignore file of its own. The core preset reads ignores from version control, and Biome looks for them only in the folder that holds `biome.jsonc`, so it stopped with "Biome couldn't find an ignore file" outside a git repository, and in a package below the repository root, until that folder had a `.gitignore`. When `init` creates `biome.jsonc` in a folder with no `.git`, `.gitignore` or `.ignore`, it now sets `vcs.root` to the repository root, or writes a `.gitignore` with `node_modules` when there's no repository.
- c9b606a: The Biome `core` preset now turns on [`noForIn`](https://biomejs.dev/linter/rules/no-for-in/) and [`noUndeclaredDependencies`](https://biomejs.dev/linter/rules/no-undeclared-dependencies/) as errors.
  
  `noForIn` reports every `for...in` loop, including guarded ones. Use `for...of` over `Object.keys()`, `Object.entries()` or an array instead. It had been off since it was a nursery rule, and stayed off when Biome 2.5 made it stable.
  
  `noUndeclaredDependencies` reports imports of packages that aren't declared in the closest `package.json`, which catches code that only works because a transitive dependency happens to be installed. It moves out of the `type-aware` preset: it's a Biome project rule, but `core` keeps the scanner out of `node_modules`, so turning it on made no measurable difference to `ultracite check` times. In a monorepo, a workspace package that imports a dependency declared only in the root `package.json` is now reported; declare the dependency in that package's own `package.json`. The ESLint preset already enforces this through `import-x/no-extraneous-dependencies` and `n/no-extraneous-import`.
- ed5ed04: The Biome `type-aware` preset no longer turns on `useImportExtensions`, which required a file extension on every relative import. The Oxlint and ESLint presets leave import extensions to the bundler and TypeScript (`import/extensions` is off), and Biome's `core` preset already had the rule off, so turning on type-aware linting no longer adds it.
- f43418c: `--hooks devin` works with Devin Local, Devin Desktop's only agent since 3.9.19. Earlier versions wrote a `post_write_code` hook to `.devin/hooks.json` for Cascade, which Devin Desktop removed, so the hook no longer ran. `init` now writes a `PostToolUse` hook to `.devin/hooks.v1.json`, in Claude Code's format, which Devin Local and [Devin CLI](https://docs.devin.ai/cli/extensibility/hooks/overview) read. Re-running `init` takes the old hook out of `.devin/hooks.json` and `.windsurf/hooks.json` and leaves your own hooks there, or removes a file left empty.
  
  Devin reads exit code 2 from a hook as "block", so when `ultracite fix --hook` runs under Devin (it sets `DEVIN_PROJECT_DIR`), it exits with 0 and prints what it couldn't fix as the hook's `hookSpecificOutput.additionalContext`, which Devin adds to the agent's context.
- ed5ed04: `ultracite init` now installs the linter's editor extension into the editor you picked. Every VS Code-based editor used to run `code --install-extension`, which put the extension in VS Code rather than in Cursor, Windsurf, Kiro or the others. Each editor now uses its own launcher: `code` for VS Code, `cursor` for Cursor, `devin-desktop` for Windsurf (now Devin Desktop, falling back to `windsurf` on installs from before the rename), `buddy` for CodeBuddy, `antigravity-ide` for Antigravity IDE, `bobide` for IBM Bob, `kiro` for Kiro, `trae` for Trae and `void` for Void. CodeBuddy's `codebuddy` command is its terminal agent, not the IDE, so init doesn't use it. When the launcher isn't on your `PATH`, init asks you to install the extension yourself, as it does when an install fails.
- f43418c: An editor extension install that takes longer than two minutes is now stopped and treated as failed, so a launcher that isn't the editor's own (such as `kiro` set to open Kiro CLI) can't hang `ultracite init`. Init then asks you to install the extension yourself, as it does for any failed install.
- ed5ed04: `init --frameworks angular` with ESLint now installs the `@angular-eslint/eslint-plugin` version the Angular preset is tested against, instead of the latest release, which could add or rename rules the preset didn't know about.
- ed5ed04: `ultracite check` and `fix` on the ESLint toolchain no longer warn about each file you pass that no ESLint config covers, such as `README.md` or `package.json`. A pre-commit hook that passes every staged file hit "File ignored because no matching configuration was supplied" on most commits. Ultracite now passes `--no-warn-ignored` to ESLint when you name files, unless you pass `--warn-ignored` or `--no-warn-ignored` yourself.
- f43418c: Antigravity IDE, CodeBuddy, Trae and Void now use the project's TypeScript version. They're built on VS Code releases before 1.111, which read `typescript.tsdk` and `typescript.enablePromptUseWorkspaceTsdk` rather than the `js/ts.tsdk.path` and `js/ts.tsdk.promptToUseWorkspaceVersion` settings `init` writes, so for those editors `init` writes both. Other editors keep only the new settings, since VS Code marks the old ones deprecated.
- e0bac18: `ultracite init --linter eslint` works with npm for React, Next.js, Astro and TanStack projects. `eslint-plugin-react`, `eslint-plugin-jsx-a11y` and `@tanstack/eslint-plugin-start` run on ESLint 10 but their `eslint` peer ranges stop at 9, so npm refused to install them next to it with `ERESOLVE unable to resolve dependency tree`. In npm projects, `init` and `upgrade` now add an [`overrides`](https://docs.npmjs.com/cli/configuring-npm/package-json#overrides) entry to `package.json` for each of those plugins that points its `eslint` peer at your own ESLint (`"eslint": "$eslint"`), so later `npm install` and `npm ci` runs work too. Overrides you already have for those packages are kept. pnpm, Yarn and Bun only warn about peer ranges, so their projects are left as they are.
- 6f5b7ba: Install the Ultracite skill where AdaL, IBM Bob and Qoder look for it. They read skills only from their own folders (`.adal/skills`, `.bob/skills`, `.qoder/skills`), never from the shared `.agents/skills`, so they never found it. `init` now installs the skill for each of them you choose in `--agents`, and for any whose folder the project already has.
- eb13a45: The `stylelint.config.mjs` that `ultracite init` writes on the ESLint toolchain now passes `ultracite check`. It was `export { default } from "ultracite/stylelint";`, which the ESLint core preset reports as a barrel file (`unicorn/no-barrel-files`), so a new project failed its first check on a file it never wrote. Init now writes `import config from "ultracite/stylelint";` followed by `export default { ...config };`, and re-running it replaces the old one-line config. A config you changed is left as it is.
- f43418c: `init --editors zed` with Oxlint now points you to the [Oxc extension](https://zed.dev/extensions/oxc), as it already did to Biome's, since Zed needs it to run Oxlint and Oxfmt. Zed's settings also stop asking for a `source.organizeImports.oxc` code action on save, which the Oxc extension doesn't provide; Oxfmt sorts imports when it formats.
- eb13a45: Zed's Oxlint settings no longer turn on type-aware linting by themselves. `init --editors zed` set `typeAware: true` for Oxlint's language server in every project, including ones without `oxlint-tsgolint` installed to run the type-aware rules. It now sets `typeAware: null`, so the language server follows `options.typeAware` in your Oxlint config, which `init --type-aware` sets. Re-running `init --editors zed` updates `.zed/settings.json`.

---

# ultracite@8.0.1
Source: https://www.ultracite.ai/changelog/ultracite-8-0-1

## Patch Changes

- 40d646a: `ultracite fix --claude` and `--codex` hand agents better information and report results more accurately:
  
  - Rule names reach the agent as they're written in the config, such as `no-unused-vars` and `typescript/no-explicit-any`, instead of Oxlint's `eslint(no-unused-vars)`.
  - ESLint diagnostics now carry the rule's description and documentation URL, read with the `json-with-metadata` formatter. Biome diagnostics carry the rule's documentation URL and its description from `biome explain`, since Biome's JSON reporter includes no help text.
  - The prompt tells the agent that the run is non-interactive, so it explains a decision it can't make in its final message instead of asking a question and waiting for an answer that can't come.
  - Files are handed over in path order, so the same project gets its fix in the same file on every run. Before each file after the first, Ultracite lints it again: an earlier file's fix can clear its issues (breaking an import cycle fixes both files), and the agent was being handed diagnostics that no longer applied. A file with nothing left is skipped.
  - A file the agent deleted, or one that no longer parses, now counts as unfixed. Before, its issues could disappear from the report and show as fixed.
- 2543859: Update the vendored `anti-slop` Oxlint plugin to upstream commit `13909c9` and enable its three new rules in the `ultracite/oxlint/anti-slop` preset. `require-readable-spacing` restores blank lines around structural boundaries — top-level declarations, multiline bindings, control flow, returns, and blocks — a pattern AI-generated code tends to pack together, while consecutive single-line bindings stay grouped at any scope ([dmmulroy/anti-slop#45](https://github.com/dmmulroy/anti-slop/pull/45)). Its autofix only inserts whitespace and never removes existing blank lines, so `ultracite fix` restores the spacing without fighting the formatter. `no-array-filter-map` rejects adjacent eager `filter`/`map` passes over arrays, and `no-reduce-accumulator-copy` rejects reducers that copy their accumulator on every iteration. Expect a one-time whitespace-only diff from `ultracite fix` after upgrading if you extend the preset (#803).
- 0a671cc: On the ESLint toolchain, `ultracite fix --hook` no longer deletes an import an agent has just added. A post-edit hook runs between the agent's edits, so the import is unused until the code that uses it lands, and `unused-imports/no-unused-imports` removed it first. The hook run now turns that rule off, as the Biome hook already skips `noUnusedImports` (#483). `no-unused-vars` still reports the import if it stays unused.
- de08bd3: The ESLint core preset no longer configures a `node` resolver for `import-x`, which needed `eslint-import-resolver-node`, a package `init` never installed. The TypeScript resolver it keeps resolves JavaScript files too.
- c13e042: `react/jsx-no-target-blank` now checks forms as well as links (`forms: true`) in the Oxlint and ESLint React presets, as Biome's `noBlankTarget` already does. The rules file `init` writes for agents now says to add `rel="noopener noreferrer"` to `target="_blank"` links instead of `rel="noopener"`, which Oxlint and ESLint report because it still sends the referrer. It also says to avoid import cycles again, which the Oxlint and ESLint core presets report.
- 9853406: The `oxlint.config.ts` that `ultracite init` writes now sets `env: core.env`. Oxlint doesn't carry `env` through `extends`, so the browser globals the core preset declares never reached projects, and rules that depend on them stayed quiet: `no-implied-eval` didn't report `setTimeout("…")` or `setInterval("…")`, and `no-eval` didn't report `window.eval(…)`. Workspace configs written by `init` now repeat `env: root.env` alongside `ignorePatterns` and `settings`, and an `.oxlintrc.json` that `init` migrates keeps its `env` on top of core's. Re-run `ultracite init` to update an existing config, or add `env: core.env` to it yourself.
- 7984c6e: The Oxlint `js-plugins` preset now enables the 32 SonarJS rules that the ESLint core preset already runs without type information, including the security rules `sonarjs/slow-regex`, `sonarjs/sql-queries`, `sonarjs/disabled-auto-escaping` and `sonarjs/dompurify-unsafe-config`. SonarJS marks these rules `requiresTypeChecking`, but they also check the syntax tree, so they work through Oxlint's JS plugin bridge. The preset had left out every marked rule.

---

# ultracite@8.0.2
Source: https://www.ultracite.ai/changelog/ultracite-8-0-2

## Patch Changes

- 9f80955: Make `ultracite fix --claude` and `--codex` judge each retry by what the previous edit actually did. An issue that's still reported gets the old note asking for a structurally different approach, but one that only appeared after the edit is now handed back as new, with the agent told to build on the fix rather than undo it. Before, a correct ARIA button pattern that then tripped `prefer-tag-over-role`, or a correct `<button>` missing its `type`, was treated as a failed fix and thrown away. When an issue needs a person's decision, the agent now lists it at the end of its final message. Ultracite stops retrying it and shows the agent's explanation in the summary, where it used to be discarded. The handoff also gets three fixes. Biome's `a11y` rules now reach the agent with their help text and documentation link, which a pattern that didn't allow digits in a rule group had dropped. A path Oxlint has no files to lint, such as a Markdown file, no longer crashes the run. And Biome's internal errors, such as `internalError/io` for a file it can't write, are no longer handed to the agent as lint issues.
- 30e03ef: Give `jsx-a11y/label-has-associated-control` in `ultracite/oxlint/react` the options the ESLint react preset already sets: `<Label>` counts as a label, `<Input>`, `<Select>`, `<Textarea>`, `<Checkbox>` and `<Radio>` count as controls, and a control is found up to three levels deep. Oxlint used to miss a `<Label>` with no control, and flagged an `<Input>` inside a `<label>`, or an input nested three deep, as unlabelled. Biome's `noLabelWithoutControl` in `ultracite/biome/core` gets the same label and control components.
- 947ca03: Turn off `promise/prefer-await-to-then` in `ultracite/oxlint/core` and `ultracite/eslint/core`, and `github/no-then` in `ultracite/oxlint/js-plugins` and `ultracite/eslint/core`. Both rules match `.then()`, `.catch()` and `.finally()` by method name, without type information, so they flagged APIs that aren't promises, such as [Zod's `.catch()` fallback](https://zod.dev/api#catch). They also flagged a fire-and-forget promise given a `.catch()` handler. Oxlint closed the false positive as [not planned](https://github.com/oxc-project/oxc/issues/22161). `promise/always-return` and `promise/catch-or-return` are now on in both presets, so an unhandled promise chain is still reported. In ESLint, `unicorn/prefer-await` moves to `ultracite/eslint/type-aware`, where it uses type information to skip calls that aren't on a promise. The test-file overrides that turned `promise/prefer-await-to-then` off in the jest and vitest presets are gone, since the rule is off everywhere.
- c198d06: Stop `unicorn/no-useless-undefined` in `ultracite/oxlint/core` from checking function call arguments. A required parameter typed `string | undefined` has to be passed `undefined` explicitly, but Oxlint flagged `consume(undefined)` and `ultracite fix` rewrote it to `consume()`, which TypeScript rejects with TS2554. The rule can't see parameter types, so it now runs with `checkArguments: false`. It still reports `let value = undefined`, `return undefined` and the rest of its checks. `ultracite/eslint/core` sets the same option. [eslint-plugin-unicorn](https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/docs/rules/no-useless-undefined.md) already skipped arguments in TypeScript files, and now skips them in JavaScript too. Biome's `noUselessUndefined` never checked arguments.

---

# v1.0.1
Source: https://www.ultracite.ai/changelog/v1-0-1

## ⚠️ Pushed to `main`

- Fix deploy script ([@haydenbleasel](https://github.com/haydenbleasel))
- Fix release ([@haydenbleasel](https://github.com/haydenbleasel))
- Add Dependabot and Release config, update package name ([@haydenbleasel](https://github.com/haydenbleasel))
- Eat own dogfood ([@haydenbleasel](https://github.com/haydenbleasel))
- Improve README ([@haydenbleasel](https://github.com/haydenbleasel))
- Create VSCode settings file ([@haydenbleasel](https://github.com/haydenbleasel))
- Update description ([@haydenbleasel](https://github.com/haydenbleasel))
- Create README.md ([@haydenbleasel](https://github.com/haydenbleasel))
- Create Stylelint configuration ([@haydenbleasel](https://github.com/haydenbleasel))
- Create Prettier configuration ([@haydenbleasel](https://github.com/haydenbleasel))
- Create ESLint configuration ([@haydenbleasel](https://github.com/haydenbleasel))
- Initial commit ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.10
Source: https://www.ultracite.ai/changelog/v1-0-10

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.11
Source: https://www.ultracite.ai/changelog/v1-0-11

## ⚠️ Pushed to `main`

- Move files to root folder ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.12
Source: https://www.ultracite.ai/changelog/v1-0-12

## ⚠️ Pushed to `main`

- Add Typescript to peerDeps ([@haydenbleasel](https://github.com/haydenbleasel))
- Fix devDeps, peerDeps, file formatting and installation ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.13
Source: https://www.ultracite.ai/changelog/v1-0-13

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.14
Source: https://www.ultracite.ai/changelog/v1-0-14

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))
- Remove React dependency ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump @typescript-eslint/parser from 5.16.0 to 5.19.0 [#10](https://github.com/haydenbleasel/harmony/pull/10) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump @typescript-eslint/eslint-plugin from 5.16.0 to 5.17.0 [#6](https://github.com/haydenbleasel/harmony/pull/6) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump stylelint from 14.6.0 to 14.6.1 [#7](https://github.com/haydenbleasel/harmony/pull/7) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint-plugin-react-hooks from 4.3.0 to 4.4.0 [#8](https://github.com/haydenbleasel/harmony/pull/8) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump prettier from 2.6.0 to 2.6.1 [#2](https://github.com/haydenbleasel/harmony/pull/2) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint from 8.11.0 to 8.12.0 [#3](https://github.com/haydenbleasel/harmony/pull/3) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint-config-next from 12.1.0 to 12.1.4 [#9](https://github.com/haydenbleasel/harmony/pull/9) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump minimist from 1.2.5 to 1.2.6 [#1](https://github.com/haydenbleasel/harmony/pull/1) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.15
Source: https://www.ultracite.ai/changelog/v1-0-15

## ⚠️ Pushed to `main`

- Update Next rules ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump @typescript-eslint/parser from 5.19.0 to 5.21.0 [#17](https://github.com/haydenbleasel/harmony/pull/17) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint-plugin-import from 2.25.4 to 2.26.0 [#11](https://github.com/haydenbleasel/harmony/pull/11) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump stylelint from 14.6.1 to 14.8.1 [#12](https://github.com/haydenbleasel/harmony/pull/12) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump prettier from 2.6.1 to 2.6.2 [#13](https://github.com/haydenbleasel/harmony/pull/13) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump prettier-plugin-tailwindcss from 0.1.8 to 0.1.10 [#14](https://github.com/haydenbleasel/harmony/pull/14) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint from 8.12.0 to 8.14.0 [#15](https://github.com/haydenbleasel/harmony/pull/15) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint-config-next from 12.1.4 to 12.1.5 [#16](https://github.com/haydenbleasel/harmony/pull/16) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump @typescript-eslint/eslint-plugin from 5.17.0 to 5.21.0 [#18](https://github.com/haydenbleasel/harmony/pull/18) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint-plugin-react-hooks from 4.4.0 to 4.5.0 [#19](https://github.com/haydenbleasel/harmony/pull/19) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump typescript from 4.6.3 to 4.6.4 [#20](https://github.com/haydenbleasel/harmony/pull/20) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.16
Source: https://www.ultracite.ai/changelog/v1-0-16

## ⚠️ Pushed to `main`

- Fix package lockfile ([@haydenbleasel](https://github.com/haydenbleasel))
- Fix new Next rules ([@haydenbleasel](https://github.com/haydenbleasel))
- Bump deps ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.17
Source: https://www.ultracite.ai/changelog/v1-0-17

## ⚠️ Pushed to `main`

- Remove extended Next configs, fix duplicate rules ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.18
Source: https://www.ultracite.ai/changelog/v1-0-18

## ⚠️ Pushed to `main`

- Attempt fixing Next format ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.19
Source: https://www.ultracite.ai/changelog/v1-0-19

## ⚠️ Pushed to `main`

- Merge branch 'main' of https://github.com/haydenbleasel/harmony ([@haydenbleasel](https://github.com/haydenbleasel))
- Use next/core-web-vitals instead of custom config ([@haydenbleasel](https://github.com/haydenbleasel))
- Revert "Attempt fixing Next format" ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.2
Source: https://www.ultracite.ai/changelog/v1-0-2

## ⚠️ Pushed to `main`

- Run auto init, generate labels ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.20
Source: https://www.ultracite.ai/changelog/v1-0-20

## 🐛 Bug Fix

- Allow HTTP header literals to break naming convention [#21](https://github.com/haydenbleasel/harmony/pull/21) ([@marktheunissen](https://github.com/marktheunissen))

## Authors: 1

- Mark Theunissen ([@marktheunissen](https://github.com/marktheunissen))

---

# v1.0.21
Source: https://www.ultracite.ai/changelog/v1-0-21

## ⚠️ Pushed to `main`

- Fix stylelint extend ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump @typescript-eslint/parser from 5.22.0 to 5.27.0 [#24](https://github.com/haydenbleasel/harmony/pull/24) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump typescript from 4.6.4 to 4.7.2 [#28](https://github.com/haydenbleasel/harmony/pull/28) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump prettier-plugin-tailwindcss from 0.1.10 to 0.1.11 [#27](https://github.com/haydenbleasel/harmony/pull/27) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint from 8.15.0 to 8.16.0 [#26](https://github.com/haydenbleasel/harmony/pull/26) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint-plugin-react from 7.29.4 to 7.30.0 [#25](https://github.com/haydenbleasel/harmony/pull/25) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump stylelint from 14.8.2 to 14.8.5 [#23](https://github.com/haydenbleasel/harmony/pull/23) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump @typescript-eslint/eslint-plugin from 5.22.0 to 5.27.0 [#22](https://github.com/haydenbleasel/harmony/pull/22) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.22
Source: https://www.ultracite.ai/changelog/v1-0-22

## ⚠️ Pushed to `main`

- Attempt to split config into core, Next and Expo ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.23
Source: https://www.ultracite.ai/changelog/v1-0-23

## ⚠️ Pushed to `main`

- Merge branch 'main' of https://github.com/haydenbleasel/harmony ([@haydenbleasel](https://github.com/haydenbleasel))
- Add react-native plugin dependency ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.24
Source: https://www.ultracite.ai/changelog/v1-0-24

## ⚠️ Pushed to `main`

- Bump deps ([@haydenbleasel](https://github.com/haydenbleasel))
- Update eslint-next.js ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.25
Source: https://www.ultracite.ai/changelog/v1-0-25

## ⚠️ Pushed to `main`

- Merge branch 'main' of https://github.com/haydenbleasel/harmony ([@haydenbleasel](https://github.com/haydenbleasel))
- Remove deprecated (?) rule ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.26
Source: https://www.ultracite.ai/changelog/v1-0-26

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.27
Source: https://www.ultracite.ai/changelog/v1-0-27

## ⚠️ Pushed to `main`

- Bump runner to Node 16 ([@haydenbleasel](https://github.com/haydenbleasel))
- Add core Jest support ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump @next/eslint-plugin-next from 12.2.3 to 12.2.5 [#36](https://github.com/haydenbleasel/harmony/pull/36) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint from 8.21.0 to 8.23.0 [#37](https://github.com/haydenbleasel/harmony/pull/37) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump @typescript-eslint/parser from 5.31.0 to 5.36.1 [#38](https://github.com/haydenbleasel/harmony/pull/38) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump stylelint from 14.9.1 to 14.11.0 [#39](https://github.com/haydenbleasel/harmony/pull/39) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump @typescript-eslint/eslint-plugin from 5.31.0 to 5.36.1 [#40](https://github.com/haydenbleasel/harmony/pull/40) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump typescript from 4.7.4 to 4.8.2 [#41](https://github.com/haydenbleasel/harmony/pull/41) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint-plugin-react from 7.30.1 to 7.31.1 [#42](https://github.com/haydenbleasel/harmony/pull/42) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump @typescript-eslint/eslint-plugin from 5.30.0 to 5.31.0 [#29](https://github.com/haydenbleasel/harmony/pull/29) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint from 8.18.0 to 8.21.0 [#30](https://github.com/haydenbleasel/harmony/pull/30) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint-plugin-jsx-a11y from 6.6.0 to 6.6.1 [#31](https://github.com/haydenbleasel/harmony/pull/31) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump @next/eslint-plugin-next from 12.2.0 to 12.2.3 [#32](https://github.com/haydenbleasel/harmony/pull/32) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump prettier-plugin-tailwindcss from 0.1.11 to 0.1.13 [#33](https://github.com/haydenbleasel/harmony/pull/33) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump @typescript-eslint/parser from 5.30.0 to 5.31.0 [#34](https://github.com/haydenbleasel/harmony/pull/34) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.28
Source: https://www.ultracite.ai/changelog/v1-0-28

## ⚠️ Pushed to `main`

- Merge branch 'main' of https://github.com/haydenbleasel/harmony ([@haydenbleasel](https://github.com/haydenbleasel))
- Fix typo ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.29
Source: https://www.ultracite.ai/changelog/v1-0-29

## ⚠️ Pushed to `main`

- Merge branch 'main' of https://github.com/haydenbleasel/harmony ([@haydenbleasel](https://github.com/haydenbleasel))
- Fix prefix for jest rules ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.3
Source: https://www.ultracite.ai/changelog/v1-0-3

## ⚠️ Pushed to `main`

- Remove index file, expose multiple exports ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.30
Source: https://www.ultracite.ai/changelog/v1-0-30

## ⚠️ Pushed to `main`

- Add jest install to docs ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.31
Source: https://www.ultracite.ai/changelog/v1-0-31

## ⚠️ Pushed to `main`

- Fix typo ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.4
Source: https://www.ultracite.ai/changelog/v1-0-4

## ⚠️ Pushed to `main`

- Fix export names ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.5
Source: https://www.ultracite.ai/changelog/v1-0-5

## ⚠️ Pushed to `main`

- Swap out package imports for paths for now ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.6
Source: https://www.ultracite.ai/changelog/v1-0-6

## ⚠️ Pushed to `main`

- Add VS Code extensions ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.7
Source: https://www.ultracite.ai/changelog/v1-0-7

## ⚠️ Pushed to `main`

- Add publishConfig ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.8
Source: https://www.ultracite.ai/changelog/v1-0-8

## ⚠️ Pushed to `main`

- Add snake_case support for APIs, disable misused-promises error ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.0.9
Source: https://www.ultracite.ai/changelog/v1-0-9

## ⚠️ Pushed to `main`

- Fix note about ESLint parserOptions ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.1.1
Source: https://www.ultracite.ai/changelog/v1-1-1

## ⚠️ Pushed to `main`

- Update description, bump minor version ([@haydenbleasel](https://github.com/haydenbleasel))
- Add eslint-plugin-node ([@haydenbleasel](https://github.com/haydenbleasel))
- Add eslint-plugin-promise ([@haydenbleasel](https://github.com/haydenbleasel))
- Fix devDeps -> peerDeps ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump @typescript-eslint/eslint-plugin from 5.36.1 to 5.42.1 [#62](https://github.com/haydenbleasel/harmony/pull/62) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump stylelint-config-idiomatic-order from 8.1.0 to 9.0.0 [#45](https://github.com/haydenbleasel/harmony/pull/45) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump typescript from 4.8.2 to 4.8.4 [#46](https://github.com/haydenbleasel/harmony/pull/46) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump stylelint-config-standard from 26.0.0 to 28.0.0 [#50](https://github.com/haydenbleasel/harmony/pull/50) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint-plugin-jest from 27.0.1 to 27.1.3 [#53](https://github.com/haydenbleasel/harmony/pull/53) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump @typescript-eslint/parser from 5.36.1 to 5.42.0 [#55](https://github.com/haydenbleasel/harmony/pull/55) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint from 8.23.0 to 8.26.0 [#56](https://github.com/haydenbleasel/harmony/pull/56) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump @next/eslint-plugin-next from 12.2.5 to 13.0.1 [#57](https://github.com/haydenbleasel/harmony/pull/57) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint-plugin-react from 7.31.1 to 7.31.10 [#58](https://github.com/haydenbleasel/harmony/pull/58) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump stylelint from 14.11.0 to 14.14.0 [#59](https://github.com/haydenbleasel/harmony/pull/59) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.1.2
Source: https://www.ultracite.ai/changelog/v1-1-2

## ⚠️ Pushed to `main`

- Add missing jest deps ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.1.3
Source: https://www.ultracite.ai/changelog/v1-1-3

## ⚠️ Pushed to `main`

- Bump deps, disable promise/no-native ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump @typescript-eslint/parser from 5.42.0 to 5.42.1 [#60](https://github.com/haydenbleasel/harmony/pull/60) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump stylelint-config-standard from 26.0.0 to 29.0.0 [#61](https://github.com/haydenbleasel/harmony/pull/61) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.1.4
Source: https://www.ultracite.ai/changelog/v1-1-4

## ⚠️ Pushed to `main`

- Add missing plugin ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.1.5
Source: https://www.ultracite.ai/changelog/v1-1-5

## ⚠️ Pushed to `main`

- Add ecmaVersion ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.1.6
Source: https://www.ultracite.ai/changelog/v1-1-6

## ⚠️ Pushed to `main`

- Replace eslint-plugin-node with eslint-plugin-n ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.1.7
Source: https://www.ultracite.ai/changelog/v1-1-7

## ⚠️ Pushed to `main`

- Fix n plugin ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.1.8
Source: https://www.ultracite.ai/changelog/v1-1-8

## ⚠️ Pushed to `main`

- Remove dumb rules ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v1.1.9
Source: https://www.ultracite.ai/changelog/v1-1-9

## ⚠️ Pushed to `main`

- Allow finally in promises ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.0.1
Source: https://www.ultracite.ai/changelog/v2-0-1

## 🐛 Bug Fix

- Harmony V2 [#83](https://github.com/beskar-co/harmony/pull/83) ([@haydenbleasel](https://github.com/haydenbleasel))

## ⚠️ Pushed to `main`

- Fix typo ([@haydenbleasel](https://github.com/haydenbleasel))
- Ensure package is public ([@haydenbleasel](https://github.com/haydenbleasel))
- Remove tsup, fix typo ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump json5 from 1.0.1 to 1.0.2 [#84](https://github.com/beskar-co/harmony/pull/84) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump @typescript-eslint/eslint-plugin from 5.42.1 to 5.47.1 [#79](https://github.com/beskar-co/harmony/pull/79) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint-plugin-react from 7.31.10 to 7.31.11 [#69](https://github.com/beskar-co/harmony/pull/69) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint-plugin-jest from 27.1.5 to 27.2.0 [#73](https://github.com/beskar-co/harmony/pull/73) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint from 8.27.0 to 8.31.0 [#74](https://github.com/beskar-co/harmony/pull/74) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump prettier from 2.7.1 to 2.8.1 [#75](https://github.com/beskar-co/harmony/pull/75) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump @next/eslint-plugin-next from 13.0.3 to 13.1.1 [#76](https://github.com/beskar-co/harmony/pull/76) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump prettier-plugin-tailwindcss from 0.1.13 to 0.2.1 [#77](https://github.com/beskar-co/harmony/pull/77) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump stylelint from 14.14.1 to 14.16.1 [#78](https://github.com/beskar-co/harmony/pull/78) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump @typescript-eslint/parser from 5.42.1 to 5.47.1 [#80](https://github.com/beskar-co/harmony/pull/80) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint-plugin-n from 15.5.1 to 15.6.0 [#81](https://github.com/beskar-co/harmony/pull/81) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump typescript from 4.8.4 to 4.9.4 [#82](https://github.com/beskar-co/harmony/pull/82) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.0.10
Source: https://www.ultracite.ai/changelog/v2-0-10

## ⚠️ Pushed to `main`

- Add FAQ ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.0.11
Source: https://www.ultracite.ai/changelog/v2-0-11

## ⚠️ Pushed to `main`

- Update push.yaml ([@haydenbleasel](https://github.com/haydenbleasel))
- Bump deps ([@haydenbleasel](https://github.com/haydenbleasel))
- Delete dependabot.yaml ([@haydenbleasel](https://github.com/haydenbleasel))
- Patch AudioWorkletGlobalScope issue ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump @typescript-eslint/parser from 5.50.0 to 5.57.0 [#112](https://github.com/beskar-co/harmony/pull/112) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump prettier-plugin-tailwindcss from 0.2.2 to 0.2.6 [#111](https://github.com/beskar-co/harmony/pull/111) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump @next/eslint-plugin-next from 13.1.6 to 13.2.4 [#110](https://github.com/beskar-co/harmony/pull/110) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint from 8.33.0 to 8.37.0 [#109](https://github.com/beskar-co/harmony/pull/109) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump prettier from 2.8.3 to 2.8.7 [#108](https://github.com/beskar-co/harmony/pull/108) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump jest from 29.4.1 to 29.5.0 [#105](https://github.com/beskar-co/harmony/pull/105) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump stylelint-config-prettier from 9.0.4 to 9.0.5 [#101](https://github.com/beskar-co/harmony/pull/101) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump stylelint-prettier from 2.0.0 to 3.0.0 [#94](https://github.com/beskar-co/harmony/pull/94) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.0.2
Source: https://www.ultracite.ai/changelog/v2-0-2

## ⚠️ Pushed to `main`

- Update package.json ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.0.3
Source: https://www.ultracite.ai/changelog/v2-0-3

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.0.4
Source: https://www.ultracite.ai/changelog/v2-0-4

## ⚠️ Pushed to `main`

- Merge branch 'main' of https://github.com/beskar-co/harmony ([@haydenbleasel](https://github.com/haydenbleasel))
- Add import/resolver settings ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.0.5
Source: https://www.ultracite.ai/changelog/v2-0-5

## ⚠️ Pushed to `main`

- Bump deps ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.0.6
Source: https://www.ultracite.ai/changelog/v2-0-6

## ⚠️ Pushed to `main`

- Temporarily disable eslint-plugin-import ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.0.7
Source: https://www.ultracite.ai/changelog/v2-0-7

## ⚠️ Pushed to `main`

- Fix typo ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.0.8
Source: https://www.ultracite.ai/changelog/v2-0-8

## ⚠️ Pushed to `main`

- Merge branch 'main' of https://github.com/beskar-co/harmony ([@haydenbleasel](https://github.com/haydenbleasel))
- Fix typo ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.0.9
Source: https://www.ultracite.ai/changelog/v2-0-9

## ⚠️ Pushed to `main`

- Add Cypress support ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump @typescript-eslint/parser from 5.48.1 to 5.50.0 [#88](https://github.com/beskar-co/harmony/pull/88) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump jest from 29.3.1 to 29.4.1 [#86](https://github.com/beskar-co/harmony/pull/86) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint-plugin-react from 7.32.0 to 7.32.2 [#87](https://github.com/beskar-co/harmony/pull/87) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint-plugin-import from 2.27.4 to 2.27.5 [#89](https://github.com/beskar-co/harmony/pull/89) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump @next/eslint-plugin-next from 13.1.2 to 13.1.6 [#90](https://github.com/beskar-co/harmony/pull/90) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump typescript from 4.9.4 to 4.9.5 [#91](https://github.com/beskar-co/harmony/pull/91) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump @typescript-eslint/eslint-plugin from 5.48.1 to 5.50.0 [#92](https://github.com/beskar-co/harmony/pull/92) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump prettier-plugin-tailwindcss from 0.2.1 to 0.2.2 [#93](https://github.com/beskar-co/harmony/pull/93) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump eslint from 8.31.0 to 8.33.0 [#85](https://github.com/beskar-co/harmony/pull/85) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.1.1
Source: https://www.ultracite.ai/changelog/v2-1-1

## ⚠️ Pushed to `main`

- Minor bump, improve release file ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.1.2
Source: https://www.ultracite.ai/changelog/v2-1-2

## ⚠️ Pushed to `main`

- Re-enable sorted imports ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.2.1
Source: https://www.ultracite.ai/changelog/v2-2-1

## ⚠️ Pushed to `main`

- Bump version ([@haydenbleasel](https://github.com/haydenbleasel))
- Fix import-order ([@haydenbleasel](https://github.com/haydenbleasel))
- Make import ordering stricter ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.2.2
Source: https://www.ultracite.ai/changelog/v2-2-2

## ⚠️ Pushed to `main`

- Add TS and TSX to espree ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.2.3
Source: https://www.ultracite.ai/changelog/v2-2-3

## ⚠️ Pushed to `main`

- Possibly fix import issue ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.2.4
Source: https://www.ultracite.ai/changelog/v2-2-4

## ⚠️ Pushed to `main`

- Add Typescript import resolver ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.2.5
Source: https://www.ultracite.ai/changelog/v2-2-5

## 🐛 Bug Fix

- Create website [#114](https://github.com/beskar-co/harmony/pull/114) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.2.6
Source: https://www.ultracite.ai/changelog/v2-2-6

## ⚠️ Pushed to `main`

- Attempt to patch AudioWorkletGlobalScope issue ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.2.7
Source: https://www.ultracite.ai/changelog/v2-2-7

## ⚠️ Pushed to `main`

- Remove AudioWorkletGlobalScope ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.2.8
Source: https://www.ultracite.ai/changelog/v2-2-8

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.3.0
Source: https://www.ultracite.ai/changelog/v2-3-0

## 🚀 Enhancement

- Migrate to opt-in config [#115](https://github.com/beskar-co/harmony/pull/115) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.3.1
Source: https://www.ultracite.ai/changelog/v2-3-1

## ⚠️ Pushed to `main`

- Fix typescript-eslint/prettier issues ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.4.0
Source: https://www.ultracite.ai/changelog/v2-4-0

## 🚀 Enhancement

- Enhance website, general updates [#116](https://github.com/beskar-co/harmony/pull/116) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.4.1
Source: https://www.ultracite.ai/changelog/v2-4-1

## ⚠️ Pushed to `main`

- Fix footer issue ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.4.2
Source: https://www.ultracite.ai/changelog/v2-4-2

## ⚠️ Pushed to `main`

- Create favicon.ico ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.4.3
Source: https://www.ultracite.ai/changelog/v2-4-3

## ⚠️ Pushed to `main`

- Fix up images and responsive layout ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.4.4
Source: https://www.ultracite.ai/changelog/v2-4-4

## ⚠️ Pushed to `main`

- Fix layout bug ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.4.5
Source: https://www.ultracite.ai/changelog/v2-4-5

## ⚠️ Pushed to `main`

- Bump deps ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump stylelint from 15.8.0 to 15.10.1 [#119](https://github.com/beskar-co/harmony/pull/119) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump stylelint from 15.8.0 to 15.10.1 in /website [#118](https://github.com/beskar-co/harmony/pull/118) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.4.6
Source: https://www.ultracite.ai/changelog/v2-4-6

## ⚠️ Pushed to `main`

- Fix eslint-plugin-prettier issue ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.5.0
Source: https://www.ultracite.ai/changelog/v2-5-0

## 🚀 Enhancement

- Add Storybook [#123](https://github.com/beskar-co/harmony/pull/123) ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump word-wrap from 1.2.3 to 1.2.4 in /website [#122](https://github.com/beskar-co/harmony/pull/122) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump semver from 6.3.0 to 6.3.1 in /website [#121](https://github.com/beskar-co/harmony/pull/121) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump semver from 6.3.0 to 6.3.1 [#120](https://github.com/beskar-co/harmony/pull/120) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.5.1
Source: https://www.ultracite.ai/changelog/v2-5-1

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.5.2
Source: https://www.ultracite.ai/changelog/v2-5-2

## ⚠️ Pushed to `main`

- Tweak jsx-a11y to support custom associated controls ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v2.5.3
Source: https://www.ultracite.ai/changelog/v2-5-3

## ⚠️ Pushed to `main`

- Automatically remove unused imports ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.0.0
Source: https://www.ultracite.ai/changelog/v3-0-0

## 💥 Breaking Change

- V3 [#125](https://github.com/haydenbleasel/eslint-config-harmony/pull/125) ([@haydenbleasel](https://github.com/haydenbleasel))

## ⚠️ Pushed to `main`

- Update push.yaml ([@haydenbleasel](https://github.com/haydenbleasel))
- Create FUNDING.yml ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump postcss from 8.4.24 to 8.4.31 [#124](https://github.com/haydenbleasel/eslint-config-harmony/pull/124) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.0.1
Source: https://www.ultracite.ai/changelog/v3-0-1

## ⚠️ Pushed to `main`

- Update eslint.config.mjs ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.0.2
Source: https://www.ultracite.ai/changelog/v3-0-2

## ⚠️ Pushed to `main`

- Update eslint.config.mjs ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.0.3
Source: https://www.ultracite.ai/changelog/v3-0-3

## ⚠️ Pushed to `main`

- Switch from Yarn to pnpm, upgrade workflow ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.0.4
Source: https://www.ultracite.ai/changelog/v3-0-4

## ⚠️ Pushed to `main`

- Fix typescript-eslint issue ([@haydenbleasel](https://github.com/haydenbleasel))
- Bump deps ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.0.5
Source: https://www.ultracite.ai/changelog/v3-0-5

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump @babel/traverse from 7.23.0 to 7.23.2 [#126](https://github.com/haydenbleasel/eslint-config-harmony/pull/126) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.0.6
Source: https://www.ultracite.ai/changelog/v3-0-6

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.0.7
Source: https://www.ultracite.ai/changelog/v3-0-7

## ⚠️ Pushed to `main`

- Detect React version ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.0.8
Source: https://www.ultracite.ai/changelog/v3-0-8

## ⚠️ Pushed to `main`

- Bump deps ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.0.9
Source: https://www.ultracite.ai/changelog/v3-0-9

## ⚠️ Pushed to `main`

- Add support for geometry coordinates ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.1.0
Source: https://www.ultracite.ai/changelog/v3-1-0

## 🚀 Enhancement

- Add support for Tailwind rules [#127](https://github.com/haydenbleasel/eslint-config-harmony/pull/127) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.1.1
Source: https://www.ultracite.ai/changelog/v3-1-1

## ⚠️ Pushed to `main`

- Update tailwindcss.mjs ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.1.10
Source: https://www.ultracite.ai/changelog/v3-1-10

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.1.11
Source: https://www.ultracite.ai/changelog/v3-1-11

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.1.2
Source: https://www.ultracite.ai/changelog/v3-1-2

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.1.3
Source: https://www.ultracite.ai/changelog/v3-1-3

## ⚠️ Pushed to `main`

- Bump deps ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.1.4
Source: https://www.ultracite.ai/changelog/v3-1-4

## ⚠️ Pushed to `main`

- Temporarily disable eslint-config-tailwindcss ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.1.5
Source: https://www.ultracite.ai/changelog/v3-1-5

## ⚠️ Pushed to `main`

- Merge branch 'main' of https://github.com/haydenbleasel/eslint-config-harmony ([@haydenbleasel](https://github.com/haydenbleasel))
- Remove ESLint 8.53 deprecated rules ([@haydenbleasel](https://github.com/haydenbleasel))
- Bump deps ([@haydenbleasel](https://github.com/haydenbleasel))
- Update settings.json ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.1.6
Source: https://www.ultracite.ai/changelog/v3-1-6

## ⚠️ Pushed to `main`

- Stylelint v15 updates ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.1.7
Source: https://www.ultracite.ai/changelog/v3-1-7

## ⚠️ Pushed to `main`

- Create SECURITY.md ([@haydenbleasel](https://github.com/haydenbleasel))
- Create license.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.1.8
Source: https://www.ultracite.ai/changelog/v3-1-8

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.1.9
Source: https://www.ultracite.ai/changelog/v3-1-9

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.2.1
Source: https://www.ultracite.ai/changelog/v3-2-1

## 🐛 Bug Fix

- Rebrand from `eslint-config-harmony` to `ultracite` [#129](https://github.com/haydenbleasel/ultracite/pull/129) ([@haydenbleasel](https://github.com/haydenbleasel))

## ⚠️ Pushed to `main`

- Update package.json ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.2.2
Source: https://www.ultracite.ai/changelog/v3-2-2

## ⚠️ Pushed to `main`

- Fix ultracite version ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.2.3
Source: https://www.ultracite.ai/changelog/v3-2-3

## ⚠️ Pushed to `main`

- Fix baseUrl on website ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.2.4
Source: https://www.ultracite.ai/changelog/v3-2-4

## ⚠️ Pushed to `main`

- Remove logo from readme ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.2.5
Source: https://www.ultracite.ai/changelog/v3-2-5

## ⚠️ Pushed to `main`

- Add Vercel Analytics to site ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.3.0
Source: https://www.ultracite.ai/changelog/v3-3-0

## 🚀 Enhancement

- Bundle [#131](https://github.com/haydenbleasel/ultracite/pull/131) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.3.1
Source: https://www.ultracite.ai/changelog/v3-3-1

## ⚠️ Pushed to `main`

- Update tsup.config.ts ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.3.2
Source: https://www.ultracite.ai/changelog/v3-3-2

## ⚠️ Pushed to `main`

- Merge branch 'main' of https://github.com/haydenbleasel/ultracite ([@haydenbleasel](https://github.com/haydenbleasel))
- Switch to config files, use default export syntax ([@haydenbleasel](https://github.com/haydenbleasel))
- Switch js to mjs files ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.3.3
Source: https://www.ultracite.ai/changelog/v3-3-3

## ⚠️ Pushed to `main`

- Fix exports in package.json ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.3.4
Source: https://www.ultracite.ai/changelog/v3-3-4

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.3.5
Source: https://www.ultracite.ai/changelog/v3-3-5

## ⚠️ Pushed to `main`

- Add better feature definitions to README ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.3.6
Source: https://www.ultracite.ai/changelog/v3-3-6

## ⚠️ Pushed to `main`

- Create apple-icon.png ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.3.7
Source: https://www.ultracite.ai/changelog/v3-3-7

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.4.0
Source: https://www.ultracite.ai/changelog/v3-4-0

## 🚀 Enhancement

- Add SonarJS plugin [#132](https://github.com/haydenbleasel/ultracite/pull/132) ([@haydenbleasel](https://github.com/haydenbleasel))

## ⚠️ Pushed to `main`

- Upgrade GitHub Actions workflow ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.4.1
Source: https://www.ultracite.ai/changelog/v3-4-1

## ⚠️ Pushed to `main`

- Bundle release notes on website on the same day ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.4.2
Source: https://www.ultracite.ai/changelog/v3-4-2

## ⚠️ Pushed to `main`

- Misc fix ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.5.0
Source: https://www.ultracite.ai/changelog/v3-5-0

## 🚀 Enhancement

- Add `eslint-plugin-html` [#133](https://github.com/haydenbleasel/ultracite/pull/133) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.5.1
Source: https://www.ultracite.ai/changelog/v3-5-1

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))
- Update settings.json ([@haydenbleasel](https://github.com/haydenbleasel))
- Add React / React DOM devDeps ([@haydenbleasel](https://github.com/haydenbleasel))
- Bump deps ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.5.2
Source: https://www.ultracite.ai/changelog/v3-5-2

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.6.0
Source: https://www.ultracite.ai/changelog/v3-6-0

## 🚀 Enhancement

- Add `eslint-plugin-compat` [#134](https://github.com/haydenbleasel/ultracite/pull/134) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.6.1
Source: https://www.ultracite.ai/changelog/v3-6-1

## ⚠️ Pushed to `main`

- Improve page design ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.6.2
Source: https://www.ultracite.ai/changelog/v3-6-2

## ⚠️ Pushed to `main`

- Add styles for GitHub Markdown alerts ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.7.0
Source: https://www.ultracite.ai/changelog/v3-7-0

## 🚀 Enhancement

- Add `eslint-plugin-unicorn` [#135](https://github.com/haydenbleasel/ultracite/pull/135) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.7.1
Source: https://www.ultracite.ai/changelog/v3-7-1

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.7.2
Source: https://www.ultracite.ai/changelog/v3-7-2

## ⚠️ Pushed to `main`

- Disable unicorn/no-keyword-prefix for React className ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.7.3
Source: https://www.ultracite.ai/changelog/v3-7-3

## ⚠️ Pushed to `main`

- Fix release pagination ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.7.4
Source: https://www.ultracite.ai/changelog/v3-7-4

## ⚠️ Pushed to `main`

- Update unicorn's preventAbbreviations allowList for Next.js ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.8.0
Source: https://www.ultracite.ai/changelog/v3-8-0

## 🚀 Enhancement

- Add `eslint-plugin-github` [#136](https://github.com/haydenbleasel/ultracite/pull/136) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.8.1
Source: https://www.ultracite.ai/changelog/v3-8-1

## ⚠️ Pushed to `main`

- Add documentation on monorepos ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.8.2
Source: https://www.ultracite.ai/changelog/v3-8-2

## ⚠️ Pushed to `main`

- Disable `no-undef-init` (interferes with `unicorn/no-null` ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.8.3
Source: https://www.ultracite.ai/changelog/v3-8-3

## ⚠️ Pushed to `main`

- Swap no-undef-init for unicorn/no-null ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.8.4
Source: https://www.ultracite.ai/changelog/v3-8-4

## ⚠️ Pushed to `main`

- Revert `eslint-plugin-unused-imports` to ESLint 8 compatible version ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.8.5
Source: https://www.ultracite.ai/changelog/v3-8-5

## ⚠️ Pushed to `main`

- Disable `sonarjs/elseif-without-else` ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.8.6
Source: https://www.ultracite.ai/changelog/v3-8-6

## ⚠️ Pushed to `main`

- Disable unicorn/no-array-callback-reference ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.9.0
Source: https://www.ultracite.ai/changelog/v3-9-0

## 🚀 Enhancement

- Add `@tanstack/eslint-plugin-query` [#137](https://github.com/haydenbleasel/ultracite/pull/137) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.9.1
Source: https://www.ultracite.ai/changelog/v3-9-1

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.9.10
Source: https://www.ultracite.ai/changelog/v3-9-10

## ⚠️ Pushed to `main`

- Ignore .next and .turbo folders by default ([@haydenbleasel](https://github.com/haydenbleasel))
- Ignore dist and build folders by default ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.9.11
Source: https://www.ultracite.ai/changelog/v3-9-11

## ⚠️ Pushed to `main`

- Fix website lockfile ([@haydenbleasel](https://github.com/haydenbleasel))
- Disable conflicting rules ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.9.2
Source: https://www.ultracite.ai/changelog/v3-9-2

## ⚠️ Pushed to `main`

- Fix main package ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.9.3
Source: https://www.ultracite.ai/changelog/v3-9-3

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.9.4
Source: https://www.ultracite.ai/changelog/v3-9-4

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.9.5
Source: https://www.ultracite.ai/changelog/v3-9-5

## ⚠️ Pushed to `main`

- Add Inspector to website ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.9.6
Source: https://www.ultracite.ai/changelog/v3-9-6

## ⚠️ Pushed to `main`

- Update next.config.mjs ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.9.7
Source: https://www.ultracite.ai/changelog/v3-9-7

## ⚠️ Pushed to `main`

- Update inspector ([@haydenbleasel](https://github.com/haydenbleasel))
- Use new eslint/js for rules ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.9.8
Source: https://www.ultracite.ai/changelog/v3-9-8

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v3.9.9
Source: https://www.ultracite.ai/changelog/v3-9-9

## ⚠️ Pushed to `main`

- Update settings.json ([@haydenbleasel](https://github.com/haydenbleasel))
- Bump website deps ([@haydenbleasel](https://github.com/haydenbleasel))
- Remove useAsync from exhaustive deps ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.0.0
Source: https://www.ultracite.ai/changelog/v4-0-0

## 💥 Breaking Change

- Switch from ESLint, Prettier and Stylelint to Biome [#140](https://github.com/haydenbleasel/ultracite/pull/140) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.0.1
Source: https://www.ultracite.ai/changelog/v4-0-1

## ⚠️ Pushed to `main`

- Disable useSimplifiedLogicExpression ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.0.2
Source: https://www.ultracite.ai/changelog/v4-0-2

## ⚠️ Pushed to `main`

- Disable useExplicitLengthCheck ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.0.3
Source: https://www.ultracite.ai/changelog/v4-0-3

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.0.4
Source: https://www.ultracite.ai/changelog/v4-0-4

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.0.5
Source: https://www.ultracite.ai/changelog/v4-0-5

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.0.6
Source: https://www.ultracite.ai/changelog/v4-0-6

## ⚠️ Pushed to `main`

- Update tailwind.css ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.0
Source: https://www.ultracite.ai/changelog/v4-1-0

## 🚀 Enhancement

- Biome 1.9.0 [#141](https://github.com/haydenbleasel/ultracite/pull/141) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.1
Source: https://www.ultracite.ai/changelog/v4-1-1

## ⚠️ Pushed to `main`

- Update website ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.10
Source: https://www.ultracite.ai/changelog/v4-1-10

## ⚠️ Pushed to `main`

- Update octokit.ts ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.11
Source: https://www.ultracite.ai/changelog/v4-1-11

## ⚠️ Pushed to `main`

- Merge branch 'main' of https://github.com/haydenbleasel/ultracite ([@haydenbleasel](https://github.com/haydenbleasel))
- Update files ([@haydenbleasel](https://github.com/haydenbleasel))
- Cleanup website deps ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.12
Source: https://www.ultracite.ai/changelog/v4-1-12

## ⚠️ Pushed to `main`

- Improve CLI ([@haydenbleasel](https://github.com/haydenbleasel))
- Update tailwind.css ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.13
Source: https://www.ultracite.ai/changelog/v4-1-13

## ⚠️ Pushed to `main`

- Resolves #147 ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump nanoid from 3.3.7 to 3.3.8 in /website [#146](https://github.com/haydenbleasel/ultracite/pull/146) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.14
Source: https://www.ultracite.ai/changelog/v4-1-14

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.15
Source: https://www.ultracite.ai/changelog/v4-1-15

## ⚠️ Pushed to `main`

- Resolves #148 ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump next from 15.0.4 to 15.1.2 in /website [#149](https://github.com/haydenbleasel/ultracite/pull/149) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.16
Source: https://www.ultracite.ai/changelog/v4-1-16

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.17
Source: https://www.ultracite.ai/changelog/v4-1-17

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.18
Source: https://www.ultracite.ai/changelog/v4-1-18

## ⚠️ Pushed to `main`

- Add basic init command ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.19
Source: https://www.ultracite.ai/changelog/v4-1-19

## ⚠️ Pushed to `main`

- Add support for init in monorepos ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.2
Source: https://www.ultracite.ai/changelog/v4-1-2

## ⚠️ Pushed to `main`

- Bump deps ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.20
Source: https://www.ultracite.ai/changelog/v4-1-20

## ⚠️ Pushed to `main`

- Revert "Add support for init in monorepos" ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.21
Source: https://www.ultracite.ai/changelog/v4-1-21

## 🐛 Bug Fix

- Update action on save config [#153](https://github.com/haydenbleasel/ultracite/pull/153) ([@haydenbarnett](https://github.com/haydenbarnett))

## Authors: 1

- Hayden Barnett ([@haydenbarnett](https://github.com/haydenbarnett))

---

# v4.1.3
Source: https://www.ultracite.ai/changelog/v4-1-3

## ⚠️ Pushed to `main`

- Update Biome ([@haydenbleasel](https://github.com/haydenbleasel))
- Update biome.json ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.4
Source: https://www.ultracite.ai/changelog/v4-1-4

## ⚠️ Pushed to `main`

- Resolves #142, resolves #143 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.5
Source: https://www.ultracite.ai/changelog/v4-1-5

## ⚠️ Pushed to `main`

- Bump biome ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.6
Source: https://www.ultracite.ai/changelog/v4-1-6

## ⚠️ Pushed to `main`

- Bump deps ([@haydenbleasel](https://github.com/haydenbleasel))
- Update biome.json ([@haydenbleasel](https://github.com/haydenbleasel))
- Update pnpm-lock.yaml ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump micromatch from 4.0.7 to 4.0.8 in /website [#144](https://github.com/haydenbleasel/ultracite/pull/144) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.7
Source: https://www.ultracite.ai/changelog/v4-1-7

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))
- Resolves #130 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.8
Source: https://www.ultracite.ai/changelog/v4-1-8

## ⚠️ Pushed to `main`

- Update push.yaml ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump cross-spawn from 7.0.3 to 7.0.6 in /website [#145](https://github.com/haydenbleasel/ultracite/pull/145) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.1.9
Source: https://www.ultracite.ai/changelog/v4-1-9

## ⚠️ Pushed to `main`

- next-forge changes ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.2.0
Source: https://www.ultracite.ai/changelog/v4-2-0

## 🚀 Enhancement

- Bump next from 15.1.2 to 15.2.3 in /website [#154](https://github.com/haydenbleasel/ultracite/pull/154) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 1

- [@dependabot[bot]](https://github.com/dependabot[bot])

---

# v4.2.1
Source: https://www.ultracite.ai/changelog/v4-2-1

## 🐛 Bug Fix

- Bump next from 15.2.3 to 15.2.4 in /website [#155](https://github.com/haydenbleasel/ultracite/pull/155) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 1

- [@dependabot[bot]](https://github.com/dependabot[bot])

---

# v4.2.10
Source: https://www.ultracite.ai/changelog/v4-2-10

## ⚠️ Pushed to `main`

- Create opengraph-image.jpg ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.2.11
Source: https://www.ultracite.ai/changelog/v4-2-11

## 🐛 Bug Fix

- Feature/mobile menu [#161](https://github.com/haydenbleasel/ultracite/pull/161) ([@chocochu](https://github.com/chocochu))

## Authors: 1

- Choco ([@chocochu](https://github.com/chocochu))

---

# v4.2.12
Source: https://www.ultracite.ai/changelog/v4-2-12

## ⚠️ Pushed to `main`

- Fix Biome version ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.2.13
Source: https://www.ultracite.ai/changelog/v4-2-13

## ⚠️ Pushed to `main`

- Allow for passing files to lint and format ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.2.2
Source: https://www.ultracite.ai/changelog/v4-2-2

## 🐛 Bug Fix

- New website [#158](https://github.com/haydenbleasel/ultracite/pull/158) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.2.3
Source: https://www.ultracite.ai/changelog/v4-2-3

## ⚠️ Pushed to `main`

- Update goals.mdx ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.2.4
Source: https://www.ultracite.ai/changelog/v4-2-4

## ⚠️ Pushed to `main`

- Update index.mdx ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.2.5
Source: https://www.ultracite.ai/changelog/v4-2-5

## ⚠️ Pushed to `main`

- Update OG image ([@haydenbleasel](https://github.com/haydenbleasel))
- Fix opengraph metadata ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.2.6
Source: https://www.ultracite.ai/changelog/v4-2-6

## ⚠️ Pushed to `main`

- Update bug_report.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.2.7
Source: https://www.ultracite.ai/changelog/v4-2-7

## ⚠️ Pushed to `main`

- Fix license ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.2.8
Source: https://www.ultracite.ai/changelog/v4-2-8

## ⚠️ Pushed to `main`

- Bump Commander ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v4.2.9
Source: https://www.ultracite.ai/changelog/v4-2-9

## 🐛 Bug Fix

- New landing page [#160](https://github.com/haydenbleasel/ultracite/pull/160) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.0
Source: https://www.ultracite.ai/changelog/v5-0-0

## 💥 Breaking Change

- Ultracite v5 [#162](https://github.com/haydenbleasel/ultracite/pull/162) ([@haydenbleasel](https://github.com/haydenbleasel))

## ⚠️ Pushed to `main`

- Update package.json ([@haydenbleasel](https://github.com/haydenbleasel))
- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.1
Source: https://www.ultracite.ai/changelog/v5-0-1

## ⚠️ Pushed to `main`

- Add support for installing in monorepos ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.10
Source: https://www.ultracite.ai/changelog/v5-0-10

## ⚠️ Pushed to `main`

- Update installer.tsx ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.11
Source: https://www.ultracite.ai/changelog/v5-0-11

## ⚠️ Pushed to `main`

- Remove -w flag from bun ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.12
Source: https://www.ultracite.ai/changelog/v5-0-12

## ⚠️ Pushed to `main`

- Bump Biome to 2.0.5 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.13
Source: https://www.ultracite.ai/changelog/v5-0-13

:tada: This release contains work from a new contributor! :tada:

Thank you, Denis Avakov ([@denis-avakov](https://github.com/denis-avakov)), for all your work!

## 🐛 Bug Fix

- Fix: Add support for comments in VS Code settings.json [#165](https://github.com/haydenbleasel/ultracite/pull/165) ([@denis-avakov](https://github.com/denis-avakov) [@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 2

- Denis Avakov ([@denis-avakov](https://github.com/denis-avakov))
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.14
Source: https://www.ultracite.ai/changelog/v5-0-14

## ⚠️ Pushed to `main`

- Run formatting ([@haydenbleasel](https://github.com/haydenbleasel))
- Parse biome.json properly ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.15
Source: https://www.ultracite.ai/changelog/v5-0-15

## ⚠️ Pushed to `main`

- Fix unit tests, handle parsing issues gracefully ([@haydenbleasel](https://github.com/haydenbleasel))
- Type parse responses correctly ([@haydenbleasel](https://github.com/haydenbleasel))
- Parse all JSON files using jsonc-parser ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.16
Source: https://www.ultracite.ai/changelog/v5-0-16

## ⚠️ Pushed to `main`

- Add more unit tests for jsonc files ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.17
Source: https://www.ultracite.ai/changelog/v5-0-17

:tada: This release contains work from a new contributor! :tada:

Thank you, Luke Nittmann ([@lnittman](https://github.com/lnittman)), for all your work!

## 🐛 Bug Fix

- feat: Add support for Claude Code and OpenAI Codex AI assistants [#166](https://github.com/haydenbleasel/ultracite/pull/166) ([@lnittman](https://github.com/lnittman) [@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 2

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))
- Luke Nittmann ([@lnittman](https://github.com/lnittman))

---

# v5.0.18
Source: https://www.ultracite.ai/changelog/v5-0-18

## ⚠️ Pushed to `main`

- Update rules.mdx ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.19
Source: https://www.ultracite.ai/changelog/v5-0-19

## ⚠️ Pushed to `main`

- Update tweets.tsx ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.2
Source: https://www.ultracite.ai/changelog/v5-0-2

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.20
Source: https://www.ultracite.ai/changelog/v5-0-20

:tada: This release contains work from new contributors! :tada:

Thanks for all your work!

:heart: null[@tommideso](https://github.com/tommideso)

:heart: Harry Evans ([@harryevans1997](https://github.com/harryevans1997))

## 🐛 Bug Fix

- feat: Add TanStack Router file convention support to useFilenamingConvention rule [#174](https://github.com/haydenbleasel/ultracite/pull/174) ([@Copilot](https://github.com/Copilot))
- Fix Yarn 4.9.2 compatibility by replacing --save-exact with -E flag [#173](https://github.com/haydenbleasel/ultracite/pull/173) ([@Copilot](https://github.com/Copilot))
- fix: replace 'npx biome' with 'npx @biomejs/biome' [#170](https://github.com/haydenbleasel/ultracite/pull/170) ([@tommideso](https://github.com/tommideso))
- feat: Add "tv" to allowed functions in linter options [#169](https://github.com/haydenbleasel/ultracite/pull/169) ([@harryevans1997](https://github.com/harryevans1997))

## ⚠️ Pushed to `main`

- Update format.ts ([@haydenbleasel](https://github.com/haydenbleasel))
- Delete package-lock.json ([@haydenbleasel](https://github.com/haydenbleasel))
- Update tweets.tsx ([@haydenbleasel](https://github.com/haydenbleasel))
- Resolves #167 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 4

- [@Copilot](https://github.com/Copilot)
- [@tommideso](https://github.com/tommideso)
- Harry Evans ([@harryevans1997](https://github.com/harryevans1997))
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.21
Source: https://www.ultracite.ai/changelog/v5-0-21

## 🐛 Bug Fix

- Fix Yarn monorepo support by removing invalid -W flag [#180](https://github.com/haydenbleasel/ultracite/pull/180) ([@Copilot](https://github.com/Copilot))

## Authors: 1

- [@Copilot](https://github.com/Copilot)

---

# v5.0.22
Source: https://www.ultracite.ai/changelog/v5-0-22

## 🐛 Bug Fix

- Add support for lefthook as git hooks manager [#178](https://github.com/haydenbleasel/ultracite/pull/178) ([@Copilot](https://github.com/Copilot))

## Authors: 1

- [@Copilot](https://github.com/Copilot)

---

# v5.0.23
Source: https://www.ultracite.ai/changelog/v5-0-23

## ⚠️ Pushed to `main`

- Update meta.json ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.24
Source: https://www.ultracite.ai/changelog/v5-0-24

## 🐛 Bug Fix

- Improve biome update flow to support both biome.json and biome.jsonc [#185](https://github.com/haydenbleasel/ultracite/pull/185) ([@Copilot](https://github.com/Copilot))

## Authors: 1

- [@Copilot](https://github.com/Copilot)

---

# v5.0.25
Source: https://www.ultracite.ai/changelog/v5-0-25

## ⚠️ Pushed to `main`

- Merge branch 'main' of https://github.com/haydenbleasel/ultracite ([@haydenbleasel](https://github.com/haydenbleasel))
- Create v5 migration guide ([@haydenbleasel](https://github.com/haydenbleasel))
- Add ESLint and Prettier migration guides ([@haydenbleasel](https://github.com/haydenbleasel))
- Update tweets.tsx ([@haydenbleasel](https://github.com/haydenbleasel))
- Create biome migration guide ([@haydenbleasel](https://github.com/haydenbleasel))
- Create llms.txt ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.26
Source: https://www.ultracite.ai/changelog/v5-0-26

## 🐛 Bug Fix

- Fix file path quoting for special characters in biome commands [#176](https://github.com/haydenbleasel/ultracite/pull/176) ([@Copilot](https://github.com/Copilot) [@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 2

- [@Copilot](https://github.com/Copilot)
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.27
Source: https://www.ultracite.ai/changelog/v5-0-27

## ⚠️ Pushed to `main`

- Update tweets.tsx ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.28
Source: https://www.ultracite.ai/changelog/v5-0-28

## 🐛 Bug Fix

- Bump @types/node from 24.0.3 to 24.0.8 [#194](https://github.com/haydenbleasel/ultracite/pull/194) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 1

- [@dependabot[bot]](https://github.com/dependabot[bot])

---

# v5.0.29
Source: https://www.ultracite.ai/changelog/v5-0-29

## ⚠️ Pushed to `main`

- Run formatter ([@haydenbleasel](https://github.com/haydenbleasel))
- Update pnpm-lock.yaml ([@haydenbleasel](https://github.com/haydenbleasel))
- Delete package-lock.json ([@haydenbleasel](https://github.com/haydenbleasel))
- Resolves #195 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.3
Source: https://www.ultracite.ai/changelog/v5-0-3

## ⚠️ Pushed to `main`

- Create dependabot.yml ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.30
Source: https://www.ultracite.ai/changelog/v5-0-30

:tada: This release contains work from a new contributor! :tada:

Thank you, Luiz Vergennes ([@luizvergennes](https://github.com/luizvergennes)), for all your work!

## 🐛 Bug Fix

- Zed Settings [#191](https://github.com/haydenbleasel/ultracite/pull/191) ([@luizvergennes](https://github.com/luizvergennes) [@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 2

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))
- Luiz Vergennes ([@luizvergennes](https://github.com/luizvergennes))

---

# v5.0.31
Source: https://www.ultracite.ai/changelog/v5-0-31

## 🐛 Bug Fix

- Add monorepos docs [#201](https://github.com/haydenbleasel/ultracite/pull/201) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.32
Source: https://www.ultracite.ai/changelog/v5-0-32

## 🐛 Bug Fix

- Bump next from 15.3.1 to 15.3.3 in /docs in the npm_and_yarn group across 1 directory [#204](https://github.com/haydenbleasel/ultracite/pull/204) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 1

- [@dependabot[bot]](https://github.com/dependabot[bot])

---

# v5.0.33
Source: https://www.ultracite.ai/changelog/v5-0-33

:tada: This release contains work from a new contributor! :tada:

Thank you, Rabah Tahraoui ([@rabah](https://github.com/rabah)), for all your work!

## 🐛 Bug Fix

- feat: update filename convention rule to support $ prefix [#206](https://github.com/haydenbleasel/ultracite/pull/206) ([@rabah](https://github.com/rabah))

## Authors: 1

- Rabah Tahraoui ([@rabah](https://github.com/rabah))

---

# v5.0.34
Source: https://www.ultracite.ai/changelog/v5-0-34

## 🐛 Bug Fix

- Upgrade to Biome 2.1.1 [#209](https://github.com/haydenbleasel/ultracite/pull/209) ([@haydenbleasel](https://github.com/haydenbleasel))
- Add option to remove other formatters during init [#198](https://github.com/haydenbleasel/ultracite/pull/198) ([@Copilot](https://github.com/Copilot) [@haydenbleasel](https://github.com/haydenbleasel))
- feat: Optimize AI assistant rules with structured markdown format [#183](https://github.com/haydenbleasel/ultracite/pull/183) ([@haydenbleasel](https://github.com/haydenbleasel) [@lnittman](https://github.com/lnittman))

## Authors: 3

- [@Copilot](https://github.com/Copilot)
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))
- Luke Nittmann ([@lnittman](https://github.com/lnittman))

---

# v5.0.35
Source: https://www.ultracite.ai/changelog/v5-0-35

## 🐛 Bug Fix

- Fix npm peer dependency conflicts when initializing Ultracite in Shadcn projects [#212](https://github.com/haydenbleasel/ultracite/pull/212) ([@Copilot](https://github.com/Copilot))

## Authors: 1

- [@Copilot](https://github.com/Copilot)

---

# v5.0.36
Source: https://www.ultracite.ai/changelog/v5-0-36

## ⚠️ Pushed to `main`

- Update sidebar.tsx ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.37
Source: https://www.ultracite.ai/changelog/v5-0-37

## ⚠️ Pushed to `main`

- Resolves #217 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.38
Source: https://www.ultracite.ai/changelog/v5-0-38

## ⚠️ Pushed to `main`

- Upgrade Biome version ([@haydenbleasel](https://github.com/haydenbleasel))
- Bump deps ([@haydenbleasel](https://github.com/haydenbleasel))
- Delete package-lock.json ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.39
Source: https://www.ultracite.ai/changelog/v5-0-39

## ⚠️ Pushed to `main`

- Update route.ts ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.4
Source: https://www.ultracite.ai/changelog/v5-0-4

## ⚠️ Pushed to `main`

- Drop schema rewrite (breaks types) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.40
Source: https://www.ultracite.ai/changelog/v5-0-40

## ⚠️ Pushed to `main`

- Update vercel.json ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.41
Source: https://www.ultracite.ai/changelog/v5-0-41

## ⚠️ Pushed to `main`

- Revert "Update vercel.json" ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.42
Source: https://www.ultracite.ai/changelog/v5-0-42

## ⚠️ Pushed to `main`

- Fix skip-ci file path ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.43
Source: https://www.ultracite.ai/changelog/v5-0-43

## ⚠️ Pushed to `main`

- Update shadcn/ui ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.44
Source: https://www.ultracite.ai/changelog/v5-0-44

## 🐛 Bug Fix

- Add Kiro IDE support with steering files integration [#220](https://github.com/haydenbleasel/ultracite/pull/220) ([@Copilot](https://github.com/Copilot))

## Authors: 1

- [@Copilot](https://github.com/Copilot)

---

# v5.0.45
Source: https://www.ultracite.ai/changelog/v5-0-45

## ⚠️ Pushed to `main`

- Update global.css ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.46
Source: https://www.ultracite.ai/changelog/v5-0-46

## ⚠️ Pushed to `main`

- Update rules.mdx ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.47
Source: https://www.ultracite.ai/changelog/v5-0-47

## ⚠️ Pushed to `main`

- Resolves #221, resolves #222 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.48
Source: https://www.ultracite.ai/changelog/v5-0-48

:tada: This release contains work from a new contributor! :tada:

Thank you, aditya ([@adiadd](https://github.com/adiadd)), for all your work!

## 🐛 Bug Fix

- fix: updating claude desktop mcp file path [#225](https://github.com/haydenbleasel/ultracite/pull/225) ([@adiadd](https://github.com/adiadd))

## Authors: 1

- aditya ([@adiadd](https://github.com/adiadd))

---

# v5.0.49
Source: https://www.ultracite.ai/changelog/v5-0-49

## ⚠️ Pushed to `main`

- Update faq.mdx ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.5
Source: https://www.ultracite.ai/changelog/v5-0-5

## ⚠️ Pushed to `main`

- Misc design fixes ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.6
Source: https://www.ultracite.ai/changelog/v5-0-6

## ⚠️ Pushed to `main`

- Merge branch 'main' of https://github.com/haydenbleasel/ultracite ([@haydenbleasel](https://github.com/haydenbleasel))
- Run Ultracite ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.7
Source: https://www.ultracite.ai/changelog/v5-0-7

## ⚠️ Pushed to `main`

- Update ultracite.mdc ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.8
Source: https://www.ultracite.ai/changelog/v5-0-8

## ⚠️ Pushed to `main`

- Update package-manager.ts ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.0.9
Source: https://www.ultracite.ai/changelog/v5-0-9

## ⚠️ Pushed to `main`

- Update tweets.tsx ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.1.0
Source: https://www.ultracite.ai/changelog/v5-1-0

:tada: This release contains work from a new contributor! :tada:

Thank you, Aman Varshney ([@AmanVarshney01](https://github.com/AmanVarshney01)), for all your work!

## 🚀 Enhancement

- 5.1 [#228](https://github.com/haydenbleasel/ultracite/pull/228) ([@haydenbleasel](https://github.com/haydenbleasel))

## 🐛 Bug Fix

- feat: migrate cli from commander.js to trpc-cli with flag support [#215](https://github.com/haydenbleasel/ultracite/pull/215) ([@AmanVarshney01](https://github.com/AmanVarshney01) [@haydenbleasel](https://github.com/haydenbleasel))
- Fix Bun detection for projects using bun.lock lockfile format [#227](https://github.com/haydenbleasel/ultracite/pull/227) ([@Copilot](https://github.com/Copilot))

## ⚠️ Pushed to `main`

- Update vscode-settings.ts ([@haydenbleasel](https://github.com/haydenbleasel))
- Update settings.json ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 3

- [@Copilot](https://github.com/Copilot)
- Aman Varshney ([@AmanVarshney01](https://github.com/AmanVarshney01))
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.1.1
Source: https://www.ultracite.ai/changelog/v5-1-1

## 🐛 Bug Fix

- Fix CLI to not prompt for features when other options are provided [#230](https://github.com/haydenbleasel/ultracite/pull/230) ([@Copilot](https://github.com/Copilot))

## Authors: 1

- [@Copilot](https://github.com/Copilot)

---

# v5.1.2
Source: https://www.ultracite.ai/changelog/v5-1-2

## 🐛 Bug Fix

- feat: add --skip-install flag to skip installing dependencies [#231](https://github.com/haydenbleasel/ultracite/pull/231) ([@AmanVarshney01](https://github.com/AmanVarshney01) [@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 2

- Aman Varshney ([@AmanVarshney01](https://github.com/AmanVarshney01))
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.1.3
Source: https://www.ultracite.ai/changelog/v5-1-3

## 🐛 Bug Fix

- Upgrade to Biome 2.2.0 [#245](https://github.com/haydenbleasel/ultracite/pull/245) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.1.4
Source: https://www.ultracite.ai/changelog/v5-1-4

## 🐛 Bug Fix

- Bump trpc-cli from 0.10.0 to 0.10.2 [#238](https://github.com/haydenbleasel/ultracite/pull/238) ([@dependabot[bot]](https://github.com/dependabot[bot]))
- Bump zod from 4.0.5 to 4.0.14 [#239](https://github.com/haydenbleasel/ultracite/pull/239) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 1

- [@dependabot[bot]](https://github.com/dependabot[bot])

---

# v5.1.5
Source: https://www.ultracite.ai/changelog/v5-1-5

## ⚠️ Pushed to `main`

- Update zero-config.tsx ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.1.6
Source: https://www.ultracite.ai/changelog/v5-1-6

## ⚠️ Pushed to `main`

- Resolves #246 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.1.7
Source: https://www.ultracite.ai/changelog/v5-1-7

## ⚠️ Pushed to `main`

- Resolves #248 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.1.8
Source: https://www.ultracite.ai/changelog/v5-1-8

## ⚠️ Pushed to `main`

- More kiro fixes ([@haydenbleasel](https://github.com/haydenbleasel))
- Fix missing Kiro option ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.1.9
Source: https://www.ultracite.ai/changelog/v5-1-9

## ⚠️ Pushed to `main`

- Run formatter ([@haydenbleasel](https://github.com/haydenbleasel))
- Improve file organization ([@haydenbleasel](https://github.com/haydenbleasel))
- Resolves #233 ([@haydenbleasel](https://github.com/haydenbleasel))
- Resolves #247 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.2.0
Source: https://www.ultracite.ai/changelog/v5-2-0

## 🚀 Enhancement

- nypm [#249](https://github.com/haydenbleasel/ultracite/pull/249) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.2.1
Source: https://www.ultracite.ai/changelog/v5-2-1

## ⚠️ Pushed to `main`

- Fix unit tests ([@haydenbleasel](https://github.com/haydenbleasel))
- Create util for updating package.json ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.2.10
Source: https://www.ultracite.ai/changelog/v5-2-10

## 🐛 Bug Fix

- Replace execSync commands with spawnSync [#259](https://github.com/haydenbleasel/ultracite/pull/259) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.2.11
Source: https://www.ultracite.ai/changelog/v5-2-11

## ⚠️ Pushed to `main`

- Increase test coverage lines from 93.61% to 94.18% ([@haydenbleasel](https://github.com/haydenbleasel))
- Increase test coverage lines from 88.43% to 93.61% ([@haydenbleasel](https://github.com/haydenbleasel))
- Increase test coverage lines from 87.22% to 88.43% ([@haydenbleasel](https://github.com/haydenbleasel))
- Add unit tests ([@haydenbleasel](https://github.com/haydenbleasel))
- Resolves #260 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.2.15
Source: https://www.ultracite.ai/changelog/v5-2-15

:tada: This release contains work from a new contributor! :tada:

Thank you, Kevin Wolf ([@kvnwolf](https://github.com/kvnwolf)), for all your work!

## 🐛 Bug Fix

- feat: ignore generated files [#216](https://github.com/haydenbleasel/ultracite/pull/216) ([@kvnwolf](https://github.com/kvnwolf) [@haydenbleasel](https://github.com/haydenbleasel))
- Potential fix for code scanning alert no. 8: Workflow does not contain permissions [#261](https://github.com/haydenbleasel/ultracite/pull/261) ([@haydenbleasel](https://github.com/haydenbleasel))

## ⚠️ Pushed to `main`

- Update push.yaml ([@haydenbleasel](https://github.com/haydenbleasel))
- Resolves #255 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 2

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))
- Kevin Wolf ([@kvnwolf](https://github.com/kvnwolf))

---

# v5.2.16
Source: https://www.ultracite.ai/changelog/v5-2-16

## ⚠️ Pushed to `main`

- Update push.yaml ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.2.17
Source: https://www.ultracite.ai/changelog/v5-2-17

## ⚠️ Pushed to `main`

- Fix unit tests ([@haydenbleasel](https://github.com/haydenbleasel))
- Resolves #263 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.2.2
Source: https://www.ultracite.ai/changelog/v5-2-2

## 🐛 Bug Fix

- Support more AI agents [#250](https://github.com/haydenbleasel/ultracite/pull/250) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.2.3
Source: https://www.ultracite.ai/changelog/v5-2-3

## ⚠️ Pushed to `main`

- Update editor rules docs ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.2.4
Source: https://www.ultracite.ai/changelog/v5-2-4

:tada: This release contains work from a new contributor! :tada:

Thank you, Melvyn ([@Melvynx](https://github.com/Melvynx)), for all your work!

## 🐛 Bug Fix

- Docs: Fix the docs with the latest version in biome [#252](https://github.com/haydenbleasel/ultracite/pull/252) ([@Melvynx](https://github.com/Melvynx))

## Authors: 1

- Melvyn ([@Melvynx](https://github.com/Melvynx))

---

# v5.2.5
Source: https://www.ultracite.ai/changelog/v5-2-5

## 🐛 Bug Fix

- DOCS : Fix error in the troubleshooting page [#257](https://github.com/haydenbleasel/ultracite/pull/257) ([@Melvynx](https://github.com/Melvynx))

## Authors: 1

- Melvyn ([@Melvynx](https://github.com/Melvynx))

---

# v5.2.6
Source: https://www.ultracite.ai/changelog/v5-2-6

## ⚠️ Pushed to `main`

- Bump deps ([@haydenbleasel](https://github.com/haydenbleasel))
- Upgrade Biome to 2.2.2 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.2.7
Source: https://www.ultracite.ai/changelog/v5-2-7

## ⚠️ Pushed to `main`

- Update pnpm-lock.yaml ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.2.8
Source: https://www.ultracite.ai/changelog/v5-2-8

## ⚠️ Pushed to `main`

- Fix recharts dep ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.2.9
Source: https://www.ultracite.ai/changelog/v5-2-9

## ⚠️ Pushed to `main`

- Resolves #205 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.3.0
Source: https://www.ultracite.ai/changelog/v5-3-0

## 🚀 Enhancement

- Update docs, misc fixes [#272](https://github.com/haydenbleasel/ultracite/pull/272) ([@haydenbleasel](https://github.com/haydenbleasel))

## 🐛 Bug Fix

- Release 5.3 [#270](https://github.com/haydenbleasel/ultracite/pull/270) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.3.1
Source: https://www.ultracite.ai/changelog/v5-3-1

## ⚠️ Pushed to `main`

- Resolves #262 ([@haydenbleasel](https://github.com/haydenbleasel))
- Update dependabot.yml ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump actions/checkout from 4 to 5 [#275](https://github.com/haydenbleasel/ultracite/pull/275) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.3.10
Source: https://www.ultracite.ai/changelog/v5-3-10

## ⚠️ Pushed to `main`

- Update ultracite.mdc ([@haydenbleasel](https://github.com/haydenbleasel))

## 🔩 Dependency Updates

- Bump vite from 6.3.5 to 7.1.5 in the npm_and_yarn group across 1 directory [#279](https://github.com/haydenbleasel/ultracite/pull/279) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 2

- [@dependabot[bot]](https://github.com/dependabot[bot])
- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.3.11
Source: https://www.ultracite.ai/changelog/v5-3-11

## 🐛 Bug Fix

- Docs update [#282](https://github.com/haydenbleasel/ultracite/pull/282) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.3.2
Source: https://www.ultracite.ai/changelog/v5-3-2

## ⚠️ Pushed to `main`

- Resolves #240 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.3.3
Source: https://www.ultracite.ai/changelog/v5-3-3

## ⚠️ Pushed to `main`

- Use local Biome schema ([@haydenbleasel](https://github.com/haydenbleasel))
- Don't emit diagnostics on unhandled files ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.3.4
Source: https://www.ultracite.ai/changelog/v5-3-4

:tada: This release contains work from a new contributor! :tada:

Thank you, David ([@thedevdavid](https://github.com/thedevdavid)), for all your work!

## 🐛 Bug Fix

- Update monorepos.mdx turbo task names [#277](https://github.com/haydenbleasel/ultracite/pull/277) ([@thedevdavid](https://github.com/thedevdavid))

## Authors: 1

- David ([@thedevdavid](https://github.com/thedevdavid))

---

# v5.3.5
Source: https://www.ultracite.ai/changelog/v5-3-5

:tada: This release contains work from a new contributor! :tada:

Thank you, Piotr Kulpinski ([@piotrkulpinski](https://github.com/piotrkulpinski)), for all your work!

## 🐛 Bug Fix

- update docs with correct cli option for integrations [#281](https://github.com/haydenbleasel/ultracite/pull/281) ([@piotrkulpinski](https://github.com/piotrkulpinski))

## Authors: 1

- Piotr Kulpinski ([@piotrkulpinski](https://github.com/piotrkulpinski))

---

# v5.3.6
Source: https://www.ultracite.ai/changelog/v5-3-6

## ⚠️ Pushed to `main`

- Update workflows ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.3.7
Source: https://www.ultracite.ai/changelog/v5-3-7

## ⚠️ Pushed to `main`

- Update build.yml ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.3.8
Source: https://www.ultracite.ai/changelog/v5-3-8

## ⚠️ Pushed to `main`

- Rename file, cleanup steps ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.3.9
Source: https://www.ultracite.ai/changelog/v5-3-9

## ⚠️ Pushed to `main`

- Update validate.yml ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.4.0
Source: https://www.ultracite.ai/changelog/v5-4-0

## 🚀 Enhancement

- Upgrade to Biome 2.2.4 [#283](https://github.com/haydenbleasel/ultracite/pull/283) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.4.1
Source: https://www.ultracite.ai/changelog/v5-4-1

## ⚠️ Pushed to `main`

- Update README.md ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.4.2
Source: https://www.ultracite.ai/changelog/v5-4-2

## ⚠️ Pushed to `main`

- Update zero-config.tsx ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.4.3
Source: https://www.ultracite.ai/changelog/v5-4-3

## ⚠️ Pushed to `main`

- Fix docs layout ([@haydenbleasel](https://github.com/haydenbleasel))
- Fix SVG attributes ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.4.4
Source: https://www.ultracite.ai/changelog/v5-4-4

## ⚠️ Pushed to `main`

- Fix nav ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.4.5
Source: https://www.ultracite.ai/changelog/v5-4-5

## ⚠️ Pushed to `main`

- Update open-in-chat.tsx ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.4.6
Source: https://www.ultracite.ai/changelog/v5-4-6

:tada: This release contains work from a new contributor! :tada:

Thank you, Daniel Costrasel ([@ohkimur](https://github.com/ohkimur)), for all your work!

## 🐛 Bug Fix

- fix: disable useNamingConvention; improve comments consistency [#289](https://github.com/haydenbleasel/ultracite/pull/289) ([@ohkimur](https://github.com/ohkimur))

## Authors: 1

- Daniel Costrasel ([@ohkimur](https://github.com/ohkimur))

---

# v5.4.7
Source: https://www.ultracite.ai/changelog/v5-4-7

## ⚠️ Pushed to `main`

- Extract and update logos ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.5.0
Source: https://www.ultracite.ai/changelog/v5-5-0

## 🚀 Enhancement

- Bump @types/node from 24.5.2 to 24.6.1 [#292](https://github.com/haydenbleasel/ultracite/pull/292) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## 🔩 Dependency Updates

- Bump @trpc/server from 11.5.1 to 11.6.0 [#291](https://github.com/haydenbleasel/ultracite/pull/291) ([@dependabot[bot]](https://github.com/dependabot[bot]))

## Authors: 1

- [@dependabot[bot]](https://github.com/dependabot[bot])

---

# v5.5.1
Source: https://www.ultracite.ai/changelog/v5-5-1

## ⚠️ Pushed to `main`

- Upgrade Biome to 2.2.5 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.5.2
Source: https://www.ultracite.ai/changelog/v5-5-2

## ⚠️ Pushed to `main`

- Update logos ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.5.3
Source: https://www.ultracite.ai/changelog/v5-5-3

## ⚠️ Pushed to `main`

- Increase branch test coverage from 89.21% → 91.02% ([@haydenbleasel](https://github.com/haydenbleasel))
- Update package.json ([@haydenbleasel](https://github.com/haydenbleasel))
- Fix unit tests ([@haydenbleasel](https://github.com/haydenbleasel))
- Add Videos section to homepage ([@haydenbleasel](https://github.com/haydenbleasel))
- Merge branch 'main' of https://github.com/haydenbleasel/ultracite ([@haydenbleasel](https://github.com/haydenbleasel))
- Resolves #280 ([@haydenbleasel](https://github.com/haydenbleasel))
- Make migration dep parsing lazier ([@haydenbleasel](https://github.com/haydenbleasel))
- Resolves #287 ([@haydenbleasel](https://github.com/haydenbleasel))
- Resolves #290 ([@haydenbleasel](https://github.com/haydenbleasel))
- Resolves #294 ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.5.4
Source: https://www.ultracite.ai/changelog/v5-5-4

## 🐛 Bug Fix

- Potential fix for code scanning alert no. 13: Workflow does not contain permissions [#297](https://github.com/haydenbleasel/ultracite/pull/297) ([@haydenbleasel](https://github.com/haydenbleasel))
- Potential fix for code scanning alert no. 12: Workflow does not contain permissions [#298](https://github.com/haydenbleasel/ultracite/pull/298) ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# v5.5.5
Source: https://www.ultracite.ai/changelog/v5-5-5

## ⚠️ Pushed to `main`

- Remove unused deps ([@haydenbleasel](https://github.com/haydenbleasel))

## Authors: 1

- Hayden Bleasel ([@haydenbleasel](https://github.com/haydenbleasel))

---

# Introduction
Source: https://www.ultracite.ai/docs

Ultracite is a highly opinionated, zero-configuration preset for JavaScript and TypeScript linting and formatting. It supports three major toolchains:

- **[Oxlint](https://oxc.rs/docs/guide/usage/linter.html) + [Oxfmt](https://oxc.rs/docs/guide/usage/formatter.html)** — The fastest linter available, 50-100x faster than ESLint (recommended)
- **[Biome](https://biomejs.dev/)** — The modern, all-in-one toolchain written in Rust
- **[ESLint](https://eslint.org/) + [Prettier](https://prettier.io/) + [Stylelint](https://stylelint.io/)** — The most mature and comprehensive linting ecosystem

Install Ultracite quickly by running:

```package-install
npx ultracite init
```

Then follow the [Usage](/docs/usage) guide to get started, or check out [Setup](/docs/setup) for more granular control.

Coming from your own ESLint, Prettier, Stylelint, Biome or Oxlint setup? [Migrate](/docs/migrate) covers moving it onto Ultracite's presets with your coding agent, all at once or progressively.

## How does Ultracite work?

Once set up, Ultracite runs mostly in the background — automatically formatting your code and applying fixes every time you save your files. Because the underlying tools are highly optimized (especially the Rust-based Biome and Oxlint), running Ultracite's checks is extremely fast and can comfortably run on every save without lag. This means you can focus on building and shipping instead of manually correcting style issues or debugging runtime errors.

## Goals

Ultracite's goals from a development perspective are:

### Lightning-fast performance

Ultracite benefits from the performance of Rust-based tools like [Biome](https://biomejs.dev/) and [Oxlint](https://oxc.rs/), enabling instant feedback even on large codebases.

### Zero-config by design

Ultracite is designed to be zero-config by default. This allows new users to get started quickly without needing to configure their linter or formatter, saving teams time when onboarding new developers.

The goal is to provide a default configuration that works for most projects, while still allowing customization for those who need it.

### Intuitive and simple

Ultracite should be as invisible as possible. Preferably, it should not require any configuration or action from the user. When feedback is needed, it should be easy to understand and act on.

### Maximum type safety

Ultracite is designed to be as type-safe as possible. The presets add lint rules that catch unsafe typing and suggest improvements, and type-aware linting adds rules that use the type checker. Turning it on also turns on `strictNullChecks` in your `tsconfig.json` files (unless it's already on through `extends` or you've explicitly turned it off), after asking.

### Plays nice with others

Ultracite works alongside other tools and libraries without conflict. You can choose the toolchain that best fits your project's needs.

## Next steps

- Run checks from the command line and your editor with the [Usage](/docs/usage) guide.
- Enforce clean commits with [Git hooks](/docs/git-hooks), or set Ultracite up across a [monorepo](/docs/monorepos).
- Wire up your AI tooling with editor [rules](/docs/ai/rules), [hooks](/docs/ai/hooks), and [skills](/docs/ai/skills).
- Upgrading from an older release? Run `npx ultracite@latest upgrade`, and see [Upgrade](/docs/upgrade) for having your coding agent update the configuration.
- Stuck on something? Check the [FAQ](/docs/faq) and [Troubleshooting](/docs/troubleshooting) pages.
- Keep up with new releases on the [changelog](/changelog).

---

# Agent Hooks
Source: https://www.ultracite.ai/docs/ai/hooks

Ultracite can automatically format and fix code after AI coding assistants make edits through hooks. This ensures all AI-generated code adheres to your project's standards without manual intervention.

The hooks work alongside your linter's formatting. After an AI coding assistant edits a file, the hook automatically runs the project's installed `ultracite fix` to format and fix auto-fixable linting issues, and in most hosts hands whatever it can't fix back to the agent. This dual approach ensures both intelligent code generation (through AI rules) and automated code quality (through hooks).

:::note
Hooks are separate from AI coding rules. The `--agents` flag configures AI coding rules, while the `--hooks` flag sets up automatic formatting after file edits.
:::

## Setup

Some tools like Cursor, Devin Desktop (formerly Windsurf), CodeBuddy, Claude Code, Codex, Deep Agents, GitHub Copilot, and Grok Build support hooks that run after AI agents edit files. Ultracite can configure these hooks automatically.

### Automatic Setup

When you run `npx ultracite init`, you'll be prompted to select which agent hooks you want to enable:

```text
? Which agent hooks do you want to enable (optional)?
  ◯ Cursor
  ◯ Devin Desktop
  ◯ CodeBuddy
  ◯ Claude Code
  ◯ Codex
  ◯ Deep Agents
  ◯ GitHub Copilot
  ◯ Grok Build
```

This will create the relevant hook configuration file in your project directory.

Ultracite writes the following files:

- Cursor: `.cursor/hooks.json`
- Devin Desktop: `.devin/hooks.v1.json`
- CodeBuddy: `.codebuddy/settings.json`
- Claude Code: `.claude/settings.json`
- Codex: `.codex/hooks.json`
- Deep Agents: `.deepagents/hooks.json`
- GitHub Copilot: `.github/hooks/ultracite.json`
- Grok Build: `.grok/hooks/ultracite.json`

Devin Desktop, formerly Windsurf, runs Devin Local, its only agent since 3.9.19, which reads hooks in Claude Code's format from `.devin/hooks.v1.json` (as Devin CLI does). Earlier versions wrote a `post_write_code` hook for Cascade, the agent Devin Local replaced, to `.devin/hooks.json`, and before that to `.windsurf/hooks.json` under the `windsurf` ID, which `--hooks` still accepts. Re-running `init` takes Ultracite's hook out of both and leaves your own hooks there, or removes a file left empty.

Grok Build uses Claude Code's format and maps its `Write|Edit` matcher onto its own file tools. It runs project hooks once you trust them with `/hooks-trust`.

Codex uses Claude Code's format too, with a matcher on `apply_patch`, the tool it edits files with; the hook reads every file the patch adds, updates or moves. Codex loads a project's `.codex/hooks.json` only once you trust the project, and runs the hook only after you review it in `/hooks`. Trust is tied to the hook's content, so when re-running `init` changes the command, Codex asks again.

Deep Agents Code (`dcode`) also uses Claude Code's format, and names its file tools `Write` and `Edit` in hook payloads. It runs a project's hooks once you trust the workspace; a headless run needs `--trust-project-hooks`.

### Hosts That Read Each Other's Hooks

Some agents also run hooks written for another tool, so a project with several Ultracite hooks can run `ultracite fix` more than once per edit. The second run finds nothing left to fix, so it only costs time.

- **Grok Build** also reads `.claude/settings.json` and `.cursor/hooks.json`, but runs a hook once when several files give it the same event, command and matcher. The Claude Code and Grok Build hooks match on all three, so together they run once. The Cursor hook has no matcher, so with it as well, Grok runs the fix twice.
- **The Copilot CLI** also reads `.claude/settings.json` and runs the hooks from every file, so with both the Claude Code and GitHub Copilot hooks it runs the fix twice. The Copilot cloud agent reads only `.github/hooks/`.

The GitHub Copilot file uses the format the Copilot CLI and cloud agent read (a numeric `version` and camelCase events), which VS Code also understands:

```json title=".github/hooks/ultracite.json"
{
  "hooks": {
    "postToolUse": [
      {
        "command": "npx ultracite fix --hook",
        "type": "command"
      }
    ]
  },
  "version": 1
}
```

### Manual Setup

If you want to manually set things up or add hooks after initialization, run:

```bash
npx ultracite init --hooks cursor devin codebuddy claude codex deepagents copilot grok
```

This keeps the project's current linter and your changes to its configs. Alternatively, you can manually create or edit the hook configuration files in your project directory and add the appropriate hook command.

## How It Works

1. **Automatic Execution**: After the AI agent edits a file, the hook runs `ultracite fix --hook` from the project's own dependencies, through the package manager's local runner (`npx`, `pnpm exec`, `bunx` and so on). It doesn't go through the `fix` script, which may run another tool in a project that already had one. So that it doesn't remove an import the agent has added but not used yet, the hook skips the unused-import fix: Biome projects pass `--skip=correctness/noUnusedImports`, and on ESLint projects `fix --hook` turns `unused-imports/no-unused-imports` off. Oxlint's `--fix` doesn't remove unused imports.
2. **Only the Edited File**: `--hook` reads the agent's hook payload from stdin and fixes just the file it names, so an edit costs one file instead of the whole project. Claude Code, CodeBuddy, Cursor, Devin Desktop, Deep Agents, GitHub Copilot in VS Code, the Copilot CLI, and Grok Build all send the path, and Codex sends the patch it applied; multi-file edits (VS Code's multi-replace and `apply_patch`) fix each file they name, and a patch that only deletes files fixes nothing. VS Code and the Copilot CLI run the hook after every tool, so a tool that doesn't edit files (like reading one) fixes nothing. A file outside the project, one that no longer exists, or one none of your linters handle (a `Dockerfile`, `.env`) is skipped. When no path can be read from the payload, the hook fixes the whole project as before. Re-running `npx ultracite init --hooks` rewrites a hook from an earlier init, including one generated before `--hook` existed or for a different package manager or linter.
3. **Code Formatting**: Ultracite formats the edited code according to your linter configuration
4. **Linting Fixes**: Auto-fixable linting issues are resolved automatically
5. **Remaining Problems Go Back to the Agent**: When issues remain that need a manual fix, the hook prints them to stderr and exits with code 2. Claude Code, CodeBuddy, Codex, Deep Agents, Grok Build, and VS Code's Local agent show a hook's stderr to the agent on that exit code, so the agent sees what's left and fixes it in its next step. Devin reads exit code 2 as "block", so there the hook exits with 0 and prints what's left as the hook's `additionalContext`, which Devin adds to the agent's context. Codex shows it in place of the patch's own result, though the edit has already been applied. Cursor's `afterFileEdit` hook doesn't pass a hook's output to the agent, and the Copilot CLI, the Copilot cloud agent and Copilot sessions on VS Code's Agent Host show it only to you. There the hook keeps the linter's own output and exit code.
6. **Seamless Integration**: The process happens transparently without interrupting your workflow

## Benefits

Using Ultracite agent hooks provides several advantages:

- **Consistency**: All AI-generated code is automatically formatted to match your style
- **Quality**: Linting issues are fixed immediately after code generation
- **Efficiency**: No need to manually run formatters or linters after AI edits
- **Standards**: Ensures AI-generated code always adheres to project standards
- **Clean Commits**: Code is properly formatted before you even review it

## Customization

Ultracite intelligently merges with existing hook configurations:

- **Preserves existing hooks**: All existing hooks and their commands remain intact
- **Avoids duplicates**: If a hook command already runs Ultracite, it won't be added again. Only hook commands are checked, so a settings file that mentions Ultracite elsewhere (in a permission rule, say) still gets the hook
- **Upgrades old hooks**: Re-running init replaces a hook command written by an earlier version (including the `fix` script commands written by v7 and earlier, and GitHub Copilot's old `PostToolUse` format) instead of adding a second hook next to it
- **Non-destructive**: Your existing hook configuration structure is maintained

You can also customize the hook behavior by modifying the hook configuration files directly if you need different formatting commands or additional post-edit actions.

---

# Agent Rules
Source: https://www.ultracite.ai/docs/ai/rules

Ultracite provides seamless integration with AI coding assistants by automatically generating agent rule files. These rules help guide AI assistants to write better, more consistent code that follows best practices.

The agent rules work alongside your linter's formatting and linting. While your linter handles code formatting and catches errors, the agent rules guide AI assistants to write better code from the start, reducing the need for fixes later.

The generated rules intentionally focus on code quality and implementation guidance instead of hardcoding formatter-specific settings like line width, quote style, or trailing commas. That keeps the rules portable across repositories while still letting each project's configured formatter stay in charge.

This dual approach ensures both automated code quality (through linting) and intelligent code generation (through AI coding rules).

## Setup

### Automatic Setup

When you run `npx ultracite init`, you'll be asked which agents you use:

```text
? Which agents do you use (optional)?
  ◯ Universal (creates AGENTS.md for Codex, Jules, Devin, and more)
  ◯ Claude Code (creates AGENTS.md, imported from your CLAUDE.md)
  ◯ Replit Agent (creates AGENTS.md and replit.md)
  ◯ Aider (creates AGENTS.md and .aider.conf.yml)
  ◯ Gemini CLI (creates AGENTS.md and .gemini/settings.json)
```

Every choice writes the rules to `AGENTS.md`, the file nearly every coding agent reads. The other options are for the agents that need one more file to see it (see [below](#agents-that-need-one-more-step)).

If `AGENTS.md` already exists, the rules go in an Ultracite block (starting at `# Ultracite Code Standards`) below your own content. Re-running `init` replaces that block in place, removes any duplicate blocks earlier versions appended, and keeps the file's line endings. The rules tell agents to run your project's installed CLI, such as `npx ultracite fix` or `pnpm exec ultracite fix`.

### Manual Setup

To set things up by hand, copy [the rules](https://github.com/haydenbleasel/ultracite/blob/main/packages/cli/src/data/rules.ts) into `AGENTS.md` at your project root, then follow the step below for your agent if it has one.

## Supported Agents

Every agent reads the rules from `AGENTS.md`. Pass its ID to `--agents`, or `universal` to write `AGENTS.md` alone:

Codex (`codex`), Jules (`jules`), Devin (`devin`), Lovable (`lovable`), Zencoder (`zencoder`), Ona (`ona`), OpenClaw (`openclaw`), Snowflake CoCo (`snowflake-coco`), Deep Agents (`deepagents`), Qoder (`qoder`), Kimi Code CLI (`kimi-code`), Xum (`xum`), Pi (`pi`), AdaL (`adal`), GitHub Copilot (`copilot`), Cline (`cline`), Amp (`amp`), OpenHands (`open-hands`), Junie (`junie`), Augment Code (`augmentcode`), IBM Bob (`bob`), Kilo Code (`kilo-code`), goose (`goose`), Warp (`warp`), Droid (`droid`), OpenCode (`opencode`), Crush (`crush`), Qwen Code (`qwen`), Kiro CLI (`kiro-cli`), Firebender (`firebender`), Cursor CLI (`cursor-cli`), Mistral Vibe (`mistral-vibe`), Vercel Agent (`vercel`), fx (`fx`), Antigravity CLI (`antigravity`), Grok Build (`grok`), Claude Code (`claude`), Gemini CLI (`gemini`), Aider (`aider`) and Replit Agent (`replit`).

### Agents That Need One More Step

| Agent | What `init` adds |
| --- | --- |
| Claude Code (`claude`) | Claude Code reads `AGENTS.md` only when the project has no `CLAUDE.md`. If yours has one, `init` adds an `@AGENTS.md` import to it. |
| Gemini CLI (`gemini`) | Gemini CLI reads `GEMINI.md` unless told otherwise, so `init` adds `AGENTS.md` to `context.fileName` in `.gemini/settings.json`, keeping `GEMINI.md`. |
| Aider (`aider`) | Aider loads no instructions file on its own, so `init` points `.aider.conf.yml` at `AGENTS.md` and has it lint each edit (see [Aider](#aider)). |
| Replit Agent (`replit`) | Replit Agent reads only `replit.md`, which it also writes itself, so `init` adds a copy of the rules there. |

Settings files are merged, not replaced: only the keys above change, and your own settings and comments stay.

### Aider

Aider loads only the files `.aider.conf.yml` lists under `read`. So for Aider, `init` merges two keys into `.aider.conf.yml`:

```yaml title=".aider.conf.yml"
read: AGENTS.md
lint-cmd: npx ultracite fix
```

Aider lints every file it edits, so `lint-cmd` makes it run `ultracite fix` on each one. When problems are left, Aider shows them to the model and asks it to fix them before moving on. If your config already sets `lint-cmd` to another linter, `init` leaves it alone: a `lint-cmd` without a language replaces Aider's per-language linters.

### Upgrading From Per-Agent Files

Earlier versions wrote the rules into each agent's own file: `.claude/CLAUDE.md`, `GEMINI.md`, `.firebender/rules/ultracite.mdc` and Aider's `ultracite.md`. Run `init` again and the rules move to `AGENTS.md`: `init` takes Ultracite's block out of those files, removes any file left with nothing else in it, and adds the import or settings the agent needs. That happens whenever one of those files still holds the rules, whichever agents you pick, because a leftover `.claude/CLAUDE.md` would stop Claude Code from reading `AGENTS.md`.

## Reusable Skills

If your AI tool supports installable reusable skills, see the [Agent Skills](/docs/ai/skills) guide. The global Ultracite skill gives you the same baseline guidance across repositories while leaving formatting decisions to each repo's configured linter and formatter.

## Benefits

Using Ultracite agent rules provides several advantages:

- **Consistency**: All AI-generated code follows the same conventions
- **Quality**: Rules enforce best practices and prevent common mistakes
- **Accessibility**: Built-in accessibility guidelines ensure inclusive code
- **Performance**: Rules promote efficient patterns and avoid anti-patterns
- **Security**: Guidelines help prevent common security vulnerabilities

## Customization

While the default rules are comprehensive, you can customize them for your specific needs:

1. **Modify existing rules**: Edit the rule files directly, but keep your changes outside the Ultracite block in shared files like `AGENTS.md`, since re-running `init` replaces it
2. **Add project-specific rules**: Append additional guidelines
3. **Disable rules**: Remove or comment out rules that don't apply to your project

---

# Agent Skills
Source: https://www.ultracite.ai/docs/ai/skills

Ultracite supports two different AI guidance layers:

1. Repo-local agent rules generated by `npx ultracite init --agents ...`
2. A reusable Ultracite skill you can install once and carry across repositories

Use the global skill when your AI tool understands `SKILL.md`-style skills and you want a shared Ultracite baseline without copying the same instructions into every repo by hand.

## Install the skill

When you run `npx ultracite init`, it offers to install the skill (and skips the question if the skill is already installed). Pass `--install-skill` to install it without being asked, for example in a `--yes` run:

```bash
npx ultracite init --install-skill
```

`init` installs the skill into your project without prompting. It runs `skills add haydenbleasel/ultracite --yes --agent universal`, plus the agents whose project folders already exist (such as `.claude`, `.codebuddy`, `.junie` or `.kiro`). `universal` is the shared `.agents/skills` folder that Codex, Cursor, GitHub Copilot, Gemini CLI, Devin, Amp, Cline, OpenCode, and more read. AdaL, IBM Bob and Qoder read only their own folders, so when you choose one of them, `init` installs the skill there too.

To choose the agents and scope yourself, including a global install that carries across repositories, run the skills CLI directly:

```bash
npx skills add haydenbleasel/ultracite
```

This installs the reusable skill bundle from the repository so compatible tools can load it as a shared capability.

## What the skill includes

The installable skill ships with:

- `skills/ultracite/SKILL.md` for the main workflow and guidance
- `skills/ultracite/references/code-standards.md` for the detailed standards reference

The skill is designed to help an agent:

- detect when Ultracite is present in a project
- choose the active linter stack
- use the right `ultracite check`, `fix`, and `doctor` commands
- follow Ultracite's code quality, accessibility, performance, and testing standards

## Formatting stays project-local

The global skill intentionally does not hardcode formatter-specific settings such as line width, quote style, semicolons, or trailing commas.

Those details should come from the repository's configured linter and formatter instead:

- Biome projects should follow `biome.jsonc`
- ESLint projects should follow ESLint plus Prettier and Stylelint
- Oxlint projects should follow Oxlint plus Oxfmt

That keeps one global skill portable across multiple repositories without forcing every repo to share the same formatting choices.

## How it fits with repo instructions

The global skill is a baseline, not a replacement for repo-specific instructions.

Use repo-local files such as `AGENTS.md`, `CLAUDE.md`, `replit.md`, or other agent-specific config when you need to add:

- architecture decisions for a single codebase
- framework or deployment details
- project-specific naming or file layout rules
- workflow notes that only apply to one repository

In practice, the best setup is usually:

1. Install the global Ultracite skill once
2. Add repo-local Ultracite agent rules where your tool supports them
3. Let the repository's formatter config control formatting details

## When to use which option

Choose repo-local agent rules when you want committed instructions inside a specific repository and need every collaborator or cloud task to inherit the same contract.

Choose the global skill when you want Ultracite available everywhere by default and prefer to keep formatting and project specifics in each repository's own configuration.

---

# Configuration
Source: https://www.ultracite.ai/docs/configuration

One of Ultracite's best features is that it's zero-config out of the box — you can just extend the base preset and get going. However, every project is different, and you might want to customize certain rules or adapt Ultracite for different frameworks.

## Framework Presets

Ultracite provides framework-specific configurations that you can extend in addition to the base `core` configuration. This allows you to add framework-specific linting rules without bloating the base config or dealing with irrelevant rules.

The concept is the same across all supported linters — pull in the `core` preset, then layer on any framework presets you need — though the exact syntax differs per linter (Biome uses an `extends` array, while ESLint and Oxlint use imports; each [provider page](/providers) shows its config files). For example, if you're using Biome with React and Next.js, you can pull in the following presets:

```jsonc title="biome.jsonc"
{
  "extends": [
    "ultracite/biome/core",
    "ultracite/biome/react",
    "ultracite/biome/next",
  ],
}
```

On Oxlint, `init` writes `oxlint.config.ts` and `oxfmt.config.ts` in an ES module package (`"type": "module"` in `package.json`) and `oxlint.config.mts` and `oxfmt.config.mts` otherwise, because Node only loads ES module syntax from a `.ts` file in an ES module package. `init` never changes `"type"`.

For the opt-in presets, such as the JS plugins that bring Oxlint closer to the ESLint preset, see [Optional Presets](/docs/presets).

## Default Configuration

When you include the `core` preset, you're pulling in Ultracite's base configuration. This preset includes framework-agnostic rules and settings. Some notable aspects:

- **TypeScript strictness**: Enables strict checks and lint rules requiring robust typing. Discourages use of `any`, requires handling of `null/undefined`, and prefers explicit types where needed.
- **Best practices**: Common rules like no unused vars, no explicit eval, no prototype pollution, etc.
- **Accessibility**: Biome's core preset enables its a11y rules (ARIA attributes, semantic HTML, keyboard navigation and more) for every project. On Oxlint and ESLint, the JSX a11y rules come with the `react` preset, and ESLint's `astro` and `svelte` presets check those templates too. ESLint's core preset adds a few that apply to every file, such as `eslint-plugin-github`'s `a11y-*` rules.
- **Formatting conventions**: 2-space indentation, 80-character line width, semicolons, trailing commas, and double quotes.

All these defaults aim to enforce consistent style and prevent common errors without manual configuration.

## Type-Aware Rules

Rules that read type information, or scan the whole project, are slower than the rest and need more setup, so every linter keeps them out of `core`. Turn them on at setup time with `npx ultracite init --type-aware`, which also turns on `strictNullChecks` in your tsconfig files.

### ESLint

The `type-aware` preset adds the `@typescript-eslint`, SonarJS and Unicorn rules that need a TypeScript program, such as `no-floating-promises`, `no-unsafe-return` and `strict-boolean-expressions`, and points the parser at your tsconfig files with the project service. `core` lints TypeScript without them, so it needs no tsconfig. Add `type-aware` straight after `core`:

```js title="eslint.config.mjs"
import core from "ultracite/eslint/core";
import typeAware from "ultracite/eslint/type-aware";
import vitest from "ultracite/eslint/vitest";
import vitestTypeAware from "ultracite/eslint/vitest/type-aware";

export default [...core, ...typeAware, ...vitest, ...vitestTypeAware];
```

Some framework plugins have type-aware rules of their own, which live in an add-on after the framework preset: `ultracite/eslint/<framework>/type-aware` for Angular, Jest, NestJS, Qwik, TanStack and Vitest. `init --type-aware` adds the add-ons for the frameworks you pick.

### Biome

The `type-aware` preset enables project-graph and type-aware rules: `noPrivateImports`, `noUnresolvedImports`, `noImportCycles`, `noDeprecatedImports`, `useJsonImportAttributes`, and `useArraySortCompare`. These rules require Biome's scanner, so they're slower and shipped as a separate layer:

```jsonc title="biome.jsonc"
{
  "extends": ["ultracite/biome/core", "ultracite/biome/type-aware"],
}
```

### Oxlint

Oxlint runs the type-aware rules `core` lists, such as `typescript/no-floating-promises`, through `oxlint-tsgolint`. `init --type-aware` installs it and sets `typeAware` in the config's `options`.

## Safe Fixes (Biome)

With Biome, `ultracite fix` runs `biome check --write`, which applies every rule's safe fixes. Fixes that Biome marks as unsafe, because they can change behavior, only run with `ultracite fix --unsafe`. The Biome preset sets `"fix": "safe"` on a few rules whose fixes Biome marks unsafe by default, so plain `ultracite fix` applies them too. These fixes are non-breaking in practice:

| Rule                 | Description                                           |
| -------------------- | ----------------------------------------------------- |
| `noUnusedImports`    | Removes unused import statements                      |
| `useBlockStatements` | Wraps single-line control flow bodies in curly braces |
| `useSortedClasses`   | Sorts Tailwind CSS classes into a consistent order    |

To stop `ultracite fix` applying one of these, override the rule in your config without the `fix` property (its fix goes back to Biome's default and only runs with `--unsafe`), or set `"fix": "none"` to turn the fix off entirely.

## Overriding Rules

Each linter has its own way to disable or modify rules. For example, to disable the `useButtonType` rule for Biome, you can do the following:

```jsonc title="biome.jsonc"
{
  "extends": ["ultracite/biome/core"],
  "linter": {
    "rules": {
      "a11y": {
        "useButtonType": "off",
      },
    },
  },
}
```

## Recipes

### Excluding Files (Biome)

Ultracite's base config uses `files.includes` to match all files while excluding common build outputs and generated code. If you need to exclude additional files or directories, add them to `files.includes` in your `biome.jsonc` with negated patterns:

```jsonc title="biome.jsonc"
{
  "extends": ["ultracite/biome/core"],
  "files": {
    "includes": ["**", "!components/ui/**", "!prisma/client", "!public"],
  },
}
```

**Important:** Always include `"**"` as the first entry. Using only negated patterns (e.g. `["!public", "!prisma/client"]`) will result in zero files being matched, because Biome needs at least one positive glob to start from.

### Browser Targets (ESLint)

`compat/compat` reports browser and JavaScript APIs your target browsers don't support. It reads the targets from your [browserslist](https://github.com/browserslist/browserslist) config. Without one, Ultracite checks against [Baseline Widely available](https://web.dev/baseline) browsers, so set your own when you support older or fewer browsers:

```json title="package.json"
{
  "browserslist": ["> 0.5%", "last 2 versions", "not dead"]
}
```

A `.browserslistrc` file works too. Ultracite looks for the config from the folder ESLint runs in, so in a monorepo that sets targets per package, run ESLint in each package or add targets at the root. For code that only runs on a server, turn the rule off with `{ rules: { "compat/compat": "off" } }`.

### Enforcing Path Aliases (Oxlint)

Ultracite's core preset does not assume a project layout, so it does not force `@/*` (or `#/*`) aliases over relative imports — that convention depends on your `tsconfig.json`, and it would false-positive in monorepos, libraries, and projects without a `src` directory. If your project maps `@/*` to `src/*` and you want to ban `../` imports between source modules, add an override scoped to `src`:

```ts title="oxlint.config.ts"
import { defineConfig } from "oxlint";
import core from "ultracite/oxlint/core";

export default defineConfig({
  env: core.env,
  extends: [core],
  ignorePatterns: core.ignorePatterns,
  overrides: [
    {
      files: ["src/**"],
      rules: {
        "import/no-relative-parent-imports": "error",
      },
    },
  ],
});
```

`import/no-relative-parent-imports` is a native Oxlint rule: it flags `../` in imports, type imports, and re-exports at any depth, while still allowing `./sibling` imports within a directory. Scoping it to `src/**` keeps tests, scripts, and config files that legitimately reach into `src` unaffected.

If you would rather point people at the alias in the diagnostic itself, use `no-restricted-imports` with a pattern instead:

```ts title="oxlint.config.ts"
overrides: [
  {
    files: ["src/**"],
    rules: {
      "no-restricted-imports": [
        "error",
        {
          patterns: [
            {
              regex: "^\\.\\./",
              message: "Use the @/* alias for imports between src modules.",
            },
          ],
        },
      ],
    },
  },
],
```

### Restricting Imports, Globals and Types

A few rules are on but report nothing until you list what to restrict, since that depends on your project:

- **Oxlint:** `no-restricted-imports`, `no-restricted-globals` and `typescript/no-restricted-types`.
- **ESLint:** the same three (`@typescript-eslint/no-restricted-types`), plus `no-restricted-syntax`, `no-restricted-exports`, `import-x/no-restricted-paths`, `import-x/prefer-namespace-import`, `n/no-restricted-import` and `n/no-restricted-require`.
- **Biome:** `noRestrictedImports` and `noRestrictedTypes`. `noRestrictedGlobals` always bans `event` and `error`, and you can add more.

Give one options in your config to use it:

```ts title="oxlint.config.ts"
rules: {
  "no-restricted-imports": [
    "error",
    {
      paths: [
        {
          name: "lodash",
          message: "Import from lodash-es, which tree-shakes.",
        },
      ],
    },
  ],
},
```

### Sorting Classes from a Custom Tailwind Theme (Oxfmt)

Tailwind class sorting uses the same algorithm as `prettier-plugin-tailwindcss`. If you use Tailwind CSS v4 with a custom theme, point Oxfmt at your stylesheet so sorting respects your custom utilities:

```ts title="oxfmt.config.ts"
import { defineConfig } from "oxfmt";
import ultracite from "ultracite/oxfmt";

export default defineConfig({
  ...ultracite,
  sortTailwindcss: {
    functions: ["clsx", "cva", "tw", "twMerge", "cn", "twJoin", "tv"],
    stylesheet: "./app/globals.css",
  },
});
```

:::note
`sortTailwindcss` is an Oxfmt option, not an Oxlint one. Put it in your Oxfmt config: Oxlint's config rejects it with `` unknown field `sortTailwindcss` ``.
:::

Setting `sortTailwindcss` replaces the preset's value instead of merging with it, so keep the preset's `functions` list.

Oxfmt resolves `stylesheet` relative to the config file that sets it. A path that doesn't resolve turns sorting off without an error, so check that classes still sort after you change it. In a monorepo with a single root config, use the path from the root, such as `./apps/web/src/styles.css`.

Oxfmt formats each file with its nearest config and doesn't merge it with the root one, so a workspace with an Oxfmt config of its own doesn't get the root's `sortTailwindcss`. The same goes for apps with different themes, since `stylesheet` takes one file. Give each of those workspaces a config that spreads the root config and points at its own stylesheet:

```ts title="apps/web/oxfmt.config.ts"
import { defineConfig } from "oxfmt";

import root from "../../oxfmt.config.ts";

export default defineConfig({
  ...root,
  sortTailwindcss: {
    functions: ["clsx", "cva", "tw", "twMerge", "cn", "twJoin", "tv"],
    stylesheet: "./src/styles.css",
  },
});
```

If the root config is `oxfmt.config.mts`, import that file instead. In a workspace whose `package.json` doesn't set `"type": "module"`, name the workspace config `oxfmt.config.mts`.

### Adding Third-Party Plugins (Oxlint)

Oxlint supports community plugins for additional rules beyond the built-in set. For example, Ultracite's Biome preset includes cognitive complexity checking via `noExcessiveCognitiveComplexity`, but Oxlint only has the standard cyclomatic `complexity` rule built in. You can close this gap with a third-party plugin like [oxlint-plugin-complexity](https://www.npmjs.com/package/oxlint-plugin-complexity):

```package-install
npm install -D oxlint-plugin-complexity
```

```ts title="oxlint.config.ts"
import { defineConfig } from "oxlint";
import core from "ultracite/oxlint/core";

export default defineConfig({
  env: core.env,
  extends: [core],
  ignorePatterns: core.ignorePatterns,
  jsPlugins: ["oxlint-plugin-complexity"],
  rules: {
    "complexity/complexity": ["error", { cognitive: 15 }],
  },
});
```

This approach lets you opt in to additional checks without Ultracite taking on third-party dependencies in its core preset.

### Effect (Oxlint)

[Effect](https://effect.website/)'s type-aware diagnostics — floating Effects, unhandled error and requirement channels, Layer and Scope mistakes, and Effect-native alternatives to `console`, `Date`, `process.env`, and friends — are available to Oxlint through [`@effect/tsgo`](https://github.com/Effect-TS/tsgo). Ultracite doesn't ship an Effect preset because the `effecttsgo` plugin isn't part of stock Oxlint: `@effect/tsgo` replaces the installed `oxlint` and `oxlint-tsgolint` binaries with builds that include it, and only supports specific versions of each. Layer it on top of `core` yourself:

```package-install
npm install -D @effect/tsgo oxlint-tsgolint
```

Patch the binaries after every install with a `prepare` script (`--no-typescript` limits the patch to Oxlint; drop it if you also want Effect's TypeScript-Go integration):

```json title="package.json"
{
  "scripts": {
    "prepare": "effect-tsgo patch --no-typescript --oxlint"
  }
}
```

Then extend one of the presets `@effect/tsgo` ships:

```ts title="oxlint.config.ts"
import { strict } from "@effect/tsgo/oxlint-presets";
import { defineConfig } from "oxlint";
import core from "ultracite/oxlint/core";

export default defineConfig({
  env: core.env,
  extends: [core, strict],
  ignorePatterns: core.ignorePatterns,
  rules: {
    "effecttsgo/global-console-in-effect": "error",
    "effecttsgo/global-date-in-effect": "error",
  },
});
```

`strict` raises every Effect diagnostic that is on by default to `error`; use `recommended` instead to keep upstream's severities. Both presets turn on Oxlint's type-aware mode, so `--type-aware` isn't needed — and core's type-aware rules, such as `typescript/no-floating-promises`, run too. Upstream leaves some rules off, like the `*-in-effect` family above; enable the ones you want in `rules`, but skip `effecttsgo/strict-boolean-expressions`, which duplicates core's `typescript/strict-boolean-expressions`. Some rules only apply to Effect 3 or Effect 4 and do nothing on the other major version — see the [rule list](https://github.com/Effect-TS/tsgo#diagnostic-status).

A few things to keep in mind:

- Unpatched Oxlint fails the whole run with `Unknown plugin: 'effecttsgo'`, so the patch has to be in place everywhere you lint, CI included.
- Reinstalling or upgrading `oxlint` or `oxlint-tsgolint` (including through `ultracite upgrade`) can restore the stock binaries without re-running `prepare`. Run `npx effect-tsgo patch --no-typescript --oxlint` again afterwards.
- The patch refuses versions it doesn't support, which fails the install. Check the supported versions in the [`@effect/tsgo` README](https://github.com/Effect-TS/tsgo#supported-package-versions) before upgrading either package.
- Effect's fixes are reported as suggestions, so `ultracite fix` only applies them with `--unsafe`.

## Rule Reference

Every rule each preset sets, and why some are off, is in the presets' source on GitHub: [Oxlint](https://github.com/haydenbleasel/ultracite/tree/main/packages/cli/config/oxlint), [Biome](https://github.com/haydenbleasel/ultracite/tree/main/packages/cli/config/biome) and [ESLint](https://github.com/haydenbleasel/ultracite/tree/main/packages/cli/config/eslint).

---

# FAQ
Source: https://www.ultracite.ai/docs/faq

## Q: What exactly is Ultracite, and how is it different from Oxlint, Biome, or ESLint?

Ultracite is essentially a preset configuration built on top of an existing toolchain. Think of Ultracite as a curated bundle of rules and settings, whereas the underlying engine — [Biome](/providers/biome), [ESLint + Prettier + Stylelint](/providers/eslint), or [Oxlint + Oxfmt](/providers/oxlint) — is what actually formats / lints code. You can use any of those tools by themselves, but you'd have to decide which rules to enable and configure their options manually. Ultracite saves you that effort by providing a ready-to-go setup that uses best practices from across the ecosystem.

Compared to ESLint + Prettier, Oxlint and Biome are faster thanks to their Rust implementations, and Biome is unified (one tool instead of two or three). If you already love tweaking every ESLint rule, Ultracite might feel restrictive; but it aims to eliminate the need for that and adopt sensible defaults.

In short: Oxlint / Biome / ESLint is the engine (linter / formatter), Ultracite is the configuration.

## Q: Do I still need ESLint or Prettier if I use Ultracite?

It depends on which provider you choose. With the default Oxlint + Oxfmt provider (or the Biome provider), Ultracite replaces the functionality of ESLint and Prettier for your JavaScript / TypeScript code — you do not need to run them at all, and it's recommended to remove those configs to avoid conflicts (init does this automatically). Ultracite's output will cover most of the formatting and linting that those tools did, usually with equivalent or stricter rules.

If you prefer to stay in the ESLint ecosystem — for example, because you rely on a specialized ESLint plugin — you can choose Ultracite's [ESLint + Prettier + Stylelint provider](/providers/eslint) instead, which gives you the same curated preset on top of those tools.

## Q: What about my non-JS/TS files? Does Ultracite handle those?

It depends on the provider. With the default Oxlint + Oxfmt, Oxlint lints JavaScript and TypeScript (including JSX/TSX and the scripts in Vue, Svelte, and Astro files) and Oxfmt formats a much wider set, including JSON, CSS, SCSS, Less, HTML, Markdown, YAML, and GraphQL. Biome lints and formats JavaScript, TypeScript, JSON, CSS, GraphQL, and HTML. With ESLint, Prettier formats most file types and Stylelint lints CSS, SCSS, and Less. See the [Languages](/docs/languages) page for a full breakdown per provider.

## Q: How often is Ultracite updated?

Ultracite is updated as needed, often following the release cycles of Oxlint, Oxfmt, and Biome. Since those tools add rules frequently, you might see frequent minor releases to Ultracite. These updates can bring new rules, bug fixes, or adjustments to defaults. `init` doesn't pin Ultracite to an exact version, so `package.json` typically records a `^x.y.z` range. Your lockfile keeps installs reproducible, and you pick up new releases when you update dependencies or run `npx ultracite upgrade`.

It's a good idea to watch the Ultracite repo for releases or check the [Releases](https://github.com/haydenbleasel/ultracite/releases) page. When updating Ultracite, read the release notes: occasionally a new rule is enabled that could surface new warnings in your project (which is a good thing for catching issues, but you should be aware of it).

Each release is verified against specific linter versions, and release notes state the minimum version required whenever that floor moves. To update Ultracite and your linter together, run `npx ultracite upgrade` — see [Upgrading](/docs/usage#upgrading). `npx ultracite doctor` tells you if the two have drifted apart.

## Q: If I disagree with a rule Ultracite enforces, what should I do?

You have a few options:

- Configure it off or to a different level in your linter config (`oxlint.config.ts` or `.mts`, `biome.jsonc`, or `eslint.config.mjs`) as a quick fix for your project. See [Configuration](/docs/configuration#overriding-rules).
- Open a [discussion](https://github.com/haydenbleasel/ultracite/discussions/) on the GitHub repo if the rule should be adjusted for everyone. The maintainers might agree it's too strict or could be optional.
- If it's a stylistic thing, remember the goal of Ultracite is to have convention over configuration: sometimes it's worth adapting to the tool's style for consistency across projects. But of course, your project's needs come first.

Ultimately, you control your project's lint config. Ultracite is a starting point; feel free to mold it, but ideally in minor ways. If you find yourself turning off a majority of rules, then Ultracite might not be the right preset for your team's preferences (though that would be uncommon).

In that case, you could build your own linter config from scratch, but you'd lose a lot of the convenience. Usually, a few tweaks are all that's needed to make Ultracite fit nicely.

## Q: Can I use Ultracite without VS Code / Cursor / Devin Desktop?

Yes. We focus on VS Code and its forks as they're the most popular IDEs for modern web development, but `init` can also write Zed settings (`--editors zed`), and every toolchain runs from the command line with `ultracite check` and `ultracite fix`, so it works in any editor or CI.

Oxlint, Biome, and ESLint each publish integrations for other editors. For Biome, see its [first-party](https://biomejs.dev/guides/editors/first-party-extensions/) and [third-party](https://biomejs.dev/guides/editors/third-party-extensions/) editor integrations.

## Q: How do I know what rules Ultracite is enforcing? Is there a list?

Yes, check the [Biome configs](https://github.com/haydenbleasel/ultracite/tree/main/packages/cli/config/biome), [Oxlint configs](https://github.com/haydenbleasel/ultracite/tree/main/packages/cli/config/oxlint), and [ESLint configs](https://github.com/haydenbleasel/ultracite/tree/main/packages/cli/config/eslint) in the GitHub repo for the rules that are enabled. Each framework (React, Next.js, etc.) has its own preset that you add alongside `core`; framework presets don't include the core rules themselves.

## Q: Can Ultracite fix all issues it finds?

Not all, but many. Ultracite will auto-fix issues that are safe and deterministic to fix. These include formatting issues and many lint errors (particularly stylistic or simple code transformations like removing unused imports, adding missing parentheses, changing `==` to `===`, etc.).

Some fixes are available but intentionally require `--unsafe` because they may change behavior. For example, Ultracite enables Biome's `noSubstr` rule, but rewriting `substring()` or `substr()` to `slice()` only happens when you run `ultracite fix --unsafe`.

More complex issues (business logic or things that require developer intention) are left for you to fix. For example, it won't magically rename variables to follow a naming convention or add missing error handling code; it will just warn you. For those, `ultracite fix --claude` or `--codex` can hand the remaining issues to an AI agent (see [AI-Powered Fixing](/docs/usage#ai-powered-fixing)).

The philosophy is similar to ESLint's: provide fixes where possible, but don't risk altering code behavior. Always review the Problems panel or CLI output for any remaining warnings after auto-fix.

## Q: Why does an import cycle go away after `ultracite fix`?

The cycle rules skip `import type`, but they don't know that TypeScript also drops a plain import whose bindings are only used as types. So an import like that counts toward a cycle in `ultracite check`, even though the cycle can't happen at runtime. `ultracite fix` rewrites it to `import type` (Biome's `useImportType`, `consistent-type-imports` in Oxlint and ESLint), and the report goes away.

The linters also differ on type-only re-exports: Oxlint follows `export type * from`, and ESLint follows `export type { … } from`. Biome doesn't resolve every import the other two do, such as tsconfig `paths` inherited through `extends`, so it can miss a cycle that crosses packages.

## Q: Does Ultracite find unused exports or files?

No. The unused-variable rules report locals and imports, but not an export another file could import, and nothing reports a file that no other file reaches. That takes a tool that reads the whole program, such as [Knip](https://knip.dev).

## Q: Where can I learn more about the tools Ultracite uses?

Each toolchain has its own documentation: [Oxlint](https://oxc.rs/docs/guide/usage/linter.html) and [Oxfmt](https://oxc.rs/docs/guide/usage/formatter.html), [Biome](https://biomejs.dev/), and [ESLint](https://eslint.org/), [Prettier](https://prettier.io/), and [Stylelint](https://stylelint.io/). If you're curious about how your linter formats code or the philosophy behind certain choices, its docs are the best resource.

Understanding the underlying tool can help you better understand Ultracite's capabilities. However, you don't need to learn it in depth to use Ultracite effectively; Ultracite's goal is to abstract those details away for most users.

## Q: How do I disable Ultracite for a specific project or file?

If you have a project where you temporarily don't want Ultracite, remove the Ultracite presets from your linter config (the `ultracite/...` imports in `oxlint.config.ts` and `oxfmt.config.ts`, or their `.mts` versions, the `extends` entries in `biome.jsonc`, or the imports in `eslint.config.mjs`), or remove the config files. If your editor's linter extension is installed, it may still format on save using the tool's defaults; to fully disable it, turn off `formatOnSave` or disable the extension for that workspace.

For a specific file, use your linter's ignore comments (`// oxlint-disable`, `// biome-ignore`, or `/* eslint-disable */`) or add the file to its ignore patterns (`ignorePatterns` for Oxlint and Oxfmt, `files.includes` for Biome, `ignores` for ESLint). Essentially, Ultracite is opt-in per project via the config: if it's not configured, it won't run.

## Q: I'm getting a corepack error during installation. What should I do?

Some users have encountered signature verification errors when running `pnpm dlx ultracite init` with corepack, particularly on Node.js v22 with older corepack versions. The error typically looks like "Cannot find matching keyid" during package installation.

Here are the recommended solutions:

- **Update corepack**: Upgrade to corepack version 0.34.0 or later. You can do this with `corepack prepare pnpm@latest --activate` or by following the [pnpm corepack setup guide](https://pnpm.io/installation#using-corepack).
- **Update Node.js**: Ultracite needs Node.js 22.18 or later, or Bun. Newer Node.js releases bundle newer corepack versions, so updating Node.js can also fix the error.
- **Use npx instead**: If corepack continues to cause issues, you can use `npx ultracite init` instead of `pnpm dlx ultracite init`.

If none of these work, please open an issue on the [Ultracite GitHub repo](https://github.com/haydenbleasel/ultracite/issues) with details about your Node.js and corepack versions.

---

We hope these FAQs clear up common points of confusion. If you have a question that isn't answered here, feel free to reach out on the project's GitHub or community channels. Ultracite is here to make your developer life easier, so feedback and questions are always welcome to help improve it!

---

# Git Hooks
Source: https://www.ultracite.ai/docs/git-hooks

Ultracite integrates with popular Git hook tools to automatically format and lint your code before every commit. This ensures all committed code follows your project's standards without manual intervention.

## Setup

During initialization, you can select which Git hook tool to use:

```bash
npx ultracite init --integrations husky lint-staged
```

Or select them interactively when prompted. In a project that's already set up, this keeps its current linter and your changes to its configs.

## Supported Tools

Every hook runs the `ultracite` installed in your project rather than downloading the latest release, so commits use the version your lockfile pins. The command depends on your package manager: `npx ultracite fix` (npm), `yarn ultracite fix`, `pnpm exec ultracite fix`, `bunx ultracite fix`, `deno run -A npm:ultracite fix`, `nub exec ultracite fix`, or `aube exec ultracite fix`. The examples below use npm.

Re-running `ultracite init` updates a hook it wrote earlier instead of adding a second one, and leaves commands you wrote yourself alone. That includes hooks from before v8, which ran `ultracite fix` on the whole project and matched fewer file types, and ones that used `pnpm dlx` or `yarn dlx`.

### Husky

[Husky](https://typicode.github.io/husky/) is a popular tool for managing Git hooks. Ultracite adds a marker-wrapped section to your `.husky/pre-commit` file. When files are staged, it runs `ultracite fix` on just those files, re-stages them, and fails the commit if any issues couldn't be auto-fixed:

```bash title=".husky/pre-commit"
# ultracite
#!/bin/sh
# Fix only the staged files
STAGED_FILES=$(git -c core.quotePath=false diff --cached --name-only --diff-filter=ACMR)
if [ -z "$STAGED_FILES" ]; then
  echo "No staged files to format"
else
  # Staged files that also have unstaged changes, found before fixing
  UNSTAGED_FILES=$(git -c core.quotePath=false diff --name-only)
  PARTIALLY_STAGED=""
  FULLY_STAGED=$STAGED_FILES
  if [ -n "$UNSTAGED_FILES" ]; then
    PARTIALLY_STAGED=$(printf '%s\n' "$STAGED_FILES" | grep -Fx -- "$UNSTAGED_FILES")
  fi
  if [ -n "$PARTIALLY_STAGED" ]; then
    FULLY_STAGED=$(printf '%s\n' "$STAGED_FILES" | grep -Fxv -- "$PARTIALLY_STAGED")
  fi

  # Run the fixer on the staged files, capturing the exit code so we can
  # still re-stage and report
  FORMAT_EXIT_CODE=0
  git diff --cached --name-only -z --diff-filter=ACMR | xargs -0 npx ultracite fix || FORMAT_EXIT_CODE=$?

  # Re-stage the fully staged files; staging the others would add their
  # unstaged changes to the commit
  printf '%s\n' "$FULLY_STAGED" | while IFS= read -r file; do
    if [ -f "$file" ]; then
      git add -- "$file"
    fi
  done

  if [ -n "$PARTIALLY_STAGED" ]; then
    echo "These files also have unstaged changes, so Ultracite's fixes to them were left unstaged. Review and stage them:"
    printf '%s\n' "$PARTIALLY_STAGED" | sed 's/^/  /'
  fi

  if [ $FORMAT_EXIT_CODE -ne 0 ]; then
    echo "Ultracite found issues that could not be auto-fixed."
    exit $FORMAT_EXIT_CODE
  fi

  echo "✨ Files formatted by Ultracite"
fi
# ultracite end
```

A file you staged only part of is fixed but not re-staged, since `git add` would also stage the changes you left out. The hook lists those files so you can review the fixes and stage them yourself; until you do, the commit takes the version you staged.

Anything you've added to the hook outside the `# ultracite` markers is preserved when Ultracite updates it, and still runs when nothing is staged. If you also select lint-staged, the section runs lint-staged (`npx lint-staged`) instead of the script above.

Ultracite also adds `husky` to your `prepare` script so hooks are installed on `npm install`. An existing `prepare` script is kept, with `&& husky` appended.

### Lefthook

[Lefthook](https://lefthook.dev/) is a fast Git hooks manager written in Go. If your project has no Lefthook config, Ultracite creates a `lefthook.yml`:

```yaml title="lefthook.yml"
pre-commit:
  jobs:
    - run: npx ultracite fix {staged_files}
      glob:
        - "*.js"
        - "*.jsx"
        - "*.mjs"
        - "*.cjs"
        - "*.ts"
        - "*.tsx"
        - "*.mts"
        - "*.cts"
        - "*.json"
        - "*.jsonc"
        - "*.css"
        - "*.scss"
        - "*.less"
        - "*.vue"
        - "*.svelte"
        - "*.astro"
        - "*.html"
        - "*.md"
        - "*.mdx"
        - "*.yaml"
        - "*.yml"
        - "*.graphql"
        - "*.gql"
      stage_fixed: true
```

Lefthook replaces `{staged_files}` with the staged files that match the globs, so only those are fixed, and `stage_fixed` re-stages them. The globs cover every file type Biome, Oxlint and Oxfmt, or ESLint, Prettier and Stylelint lint or format. With Lefthook's default glob matcher, `*.js` matches files in every directory, including the project root. If your config sets `glob_matcher: doublestar`, Ultracite writes `**/*.js`-style globs instead.

If you already have a Lefthook config, Ultracite edits the one Lefthook actually loads (`lefthook.yml`, `.lefthook.yml`, `.config/lefthook.yml`, or their `.yaml` variants) and adds the job first in `pre-commit`, keeping your comments and formatting. JSON and TOML configs aren't edited: Ultracite prints the job to add instead. Ultracite also appends `lefthook install` to your `prepare` script, keeping any existing command.

### lint-staged

[lint-staged](https://github.com/lint-staged/lint-staged) runs linters only on staged files. If your project has no lint-staged config, Ultracite creates a `.lintstagedrc.json`:

```json title=".lintstagedrc.json"
{
  "*.{js,jsx,mjs,cjs,ts,tsx,mts,cts,json,jsonc,css,scss,less,vue,svelte,astro,html,md,mdx,yaml,yml,graphql,gql}": [
    "npx ultracite fix"
  ]
}
```

If you already have one, Ultracite adds its task to the config lint-staged actually uses: a dedicated config file (`.lintstagedrc` in any format, including `.ts`, `.mts`, and `.cts`, or `lint-staged.config.*`) wins over a `"lint-staged"` key in `package.json`, which wins over one in `package.yaml`. YAML configs keep their comments, ES module and TypeScript configs are edited in place, and CommonJS configs are rewritten from their loaded values. If a config can't be merged safely (for example, one that exports a function or wraps its object in `defineConfig()`), Ultracite leaves it untouched and prints the command to add, rather than creating a second config that would shadow yours.

The glob covers the same file types as the Lefthook globs, in every directory, and lint-staged passes the staged files that match it to `ultracite fix` and re-stages them. Re-running `init` widens the narrower glob earlier versions wrote (`*.{js,jsx,ts,tsx,json,jsonc,css,scss,md,mdx}`) while its task is still only Ultracite's command.

lint-staged needs a Git hook to trigger it, so it's typically used alongside Husky or Lefthook.

### pre-commit

[pre-commit](https://pre-commit.com/) is a Python-based framework for managing Git hooks. Ultracite creates a `.pre-commit-config.yaml`, or adds a local repo entry to the top of your existing one, keeping its comments and indentation style:

```yaml title=".pre-commit-config.yaml"
repos:
  - repo: local
    hooks:
      - id: ultracite
        name: ultracite
        entry: npx ultracite fix
        language: system
        files: \.(js|jsx|mjs|cjs|ts|tsx|mts|cts|json|jsonc|css|scss|less|vue|svelte|astro|html|md|mdx|yaml|yml|graphql|gql)$
        require_serial: true
```

The `files` pattern covers the same file types as the Lefthook globs. It's a pattern rather than `types_or` because pre-commit has no file type tags for `.jsonc`, `.mts`, `.cts`, or `.gql`. pre-commit passes the staged files that match it to `ultracite fix`, and sets your unstaged changes aside while the hook runs. `require_serial` keeps it to a single `ultracite fix` run instead of one per CPU. If the fixes change any files, pre-commit stops the commit so you can stage them. After setup, run `pre-commit install` to activate the hooks.

## How It Works

1. You make changes and stage files with `git add`
2. You run `git commit`
3. The pre-commit hook runs `ultracite fix` on the files you staged
4. Code is formatted, auto-fixable issues are resolved, and the fixed files are re-staged (Husky, Lefthook, and lint-staged; pre-commit asks you to stage them)
5. The commit proceeds, or stops if issues remain that couldn't be auto-fixed

## Benefits

- **Consistency**: All committed code follows the same standards
- **Automation**: No need to remember to format code manually
- **Clean History**: Formatting issues never enter your repository
- **Team Collaboration**: Everyone follows the same rules automatically

## Bypassing Hooks

In rare cases where you need to skip the pre-commit hook:

```bash
git commit --no-verify
```

Use this sparingly, as it bypasses the automated formatting.

---

# Language Support
Source: https://www.ultracite.ai/docs/languages

Each of the tools Ultracite wraps has a different coverage story. Biome and Oxlint/Oxfmt are Rust-based and lean on what their own parsers natively support. ESLint and Prettier lean heavily on their plugin ecosystems, which means wider coverage but more moving parts. Stylelint is CSS-focused by design.

This page summarizes what each tool supports natively today so you can choose a toolchain that fits the languages your project actually uses.

## Legend

| Symbol | Meaning                                               |
| ------ | ----------------------------------------------------- |
| ✅     | Full, stable native support                           |
| 🟡     | Experimental or partial (e.g. `<script>` blocks only) |
| ⌛     | In progress per official docs                         |
| 🔌     | Supported via an official or community plugin         |
| ❌     | Not supported                                         |

## Linting Support

| Language   | Biome | Oxlint     | ESLint | Stylelint |
| ---------- | ----- | ---------- | ------ | --------- |
| JavaScript | ✅    | ✅         | ✅     | ❌        |
| TypeScript | ✅    | ✅         | 🔌     | ❌        |
| JSX        | ✅    | ✅         | ✅     | ❌        |
| TSX        | ✅    | ✅         | 🔌     | ❌        |
| JSON       | ✅    | ❌         | 🔌     | ❌        |
| JSONC      | ✅    | ❌         | 🔌     | ❌        |
| CSS        | ✅    | ❌         | 🔌     | ✅        |
| SCSS       | ❌    | ❌         | ❌     | 🔌        |
| Sass       | ❌    | ❌         | ❌     | ❌        |
| Less       | ❌    | ❌         | ❌     | 🔌        |
| HTML       | ✅    | ❌         | 🔌     | 🔌        |
| Vue        | 🟡    | 🟡 scripts | 🔌     | 🔌        |
| Svelte     | 🟡    | 🟡 scripts | 🔌     | 🔌        |
| Astro      | 🟡    | 🟡 scripts | 🔌     | 🔌        |
| GraphQL    | ✅    | ❌         | 🔌     | ❌        |
| Markdown   | ❌    | ❌         | 🔌     | ❌        |
| MDX        | ❌    | ❌         | 🔌     | ❌        |
| YAML       | ❌    | ❌         | 🔌     | ❌        |

## Formatting Support

| Language   | Biome | Oxfmt | Prettier |
| ---------- | ----- | ----- | -------- |
| JavaScript | ✅    | ✅    | ✅       |
| TypeScript | ✅    | ✅    | ✅       |
| JSX        | ✅    | ✅    | ✅       |
| TSX        | ✅    | ✅    | ✅       |
| JSON       | ✅    | ✅    | ✅       |
| JSONC      | ✅    | ✅    | ✅       |
| CSS        | ✅    | ✅    | ✅       |
| SCSS       | ⌛    | ✅    | ✅       |
| Sass       | ❌    | ❌    | ❌       |
| Less       | ❌    | ✅    | ✅       |
| HTML       | ✅    | ✅    | ✅       |
| Vue        | 🟡    | ✅    | ✅       |
| Svelte     | 🟡    | 🟡    | 🔌       |
| Astro      | 🟡    | 🟡    | 🔌       |
| GraphQL    | ✅    | ✅    | ✅       |
| Markdown   | ⌛    | ✅    | ✅       |
| MDX        | ❌    | ✅    | ✅       |
| YAML       | ⌛    | ✅    | ✅       |

## Notes

### Biome

Biome is the only tool here that explicitly tracks parse, format, and lint support per language as separate columns. The [official language-support matrix](https://biomejs.dev/internals/language-support/) is the source of truth. Vue, Svelte, and Astro are flagged as experimental and subject to change. SCSS, YAML, and Markdown are listed as in-progress for formatting, with linting not yet started.

### Oxlint

Oxlint is a JavaScript and TypeScript linter — that's it. For framework files (`.vue`, `.svelte`, `.astro`) it lints only the `<script>` block; templates are not parsed. If you need linting for CSS, JSON, YAML, or similar formats, Oxlint is not the right tool and you'll need to pair it with something else.

### Oxfmt

Oxfmt targets Prettier-style formatting breadth and is much wider than Oxlint. Its docs list JavaScript, JSX, TypeScript, TSX, JSON, JSONC, JSON5, YAML, TOML, HTML, Angular, Vue, CSS, SCSS, Less, Markdown, MDX, GraphQL, Ember, and Handlebars as supported. Svelte and Astro currently land in the partial/experimental bucket across the Oxc stack.

### ESLint

Core ESLint only parses JavaScript (and JSX with `ecmaFeatures.jsx`). Everything else — TypeScript, Vue, Svelte, Astro, JSON, YAML, Markdown, HTML, CSS — requires a custom parser or dedicated plugin (`@typescript-eslint`, `eslint-plugin-vue`, `@eslint/json`, `@eslint/markdown`, `@eslint/css`, etc.). That plugin ecosystem is by far the largest of any tool on this page, but it comes with more configuration surface area. Ultracite's ESLint preset lints JavaScript and TypeScript modules and inline scripts in HTML, plus Vue, Svelte, and Astro files through their framework presets. It doesn't lint JSON, Markdown, or YAML; Prettier formats those.

### Prettier

Prettier ships the widest built-in language coverage of any tool here, including Vue and Angular templates natively. Svelte and Astro are the notable exceptions: both are commonly used but rely on community plugins (`prettier-plugin-svelte`, `prettier-plugin-astro`). Indented Sass (`.sass`) isn't supported.

### Stylelint

Stylelint natively handles CSS. Other CSS-adjacent syntaxes — SCSS, Less, CSS-in-JS, `<style>` blocks inside HTML or framework files — work through PostCSS custom-syntax plugins (`postcss-scss`, `postcss-less`, `postcss-html`, and so on). It does not lint JavaScript, TypeScript, JSON, or other non-style formats. Ultracite's Stylelint preset lints `.css`, `.scss`, and `.less` files (`init` installs `postcss-scss` and `postcss-less`); indented Sass (`.sass`) isn't linted.

## Choosing a toolchain

Three quick rules of thumb:

- If your project is primarily **JavaScript, TypeScript, JSON, CSS, and GraphQL**, Biome gives you the tightest, fastest single-binary experience.
- If you need the **widest language coverage** or rely on language-specific ecosystem rules (e.g. deep Vue, Svelte, or Astro tooling), ESLint + Prettier + Stylelint is still the most complete option.
- If **raw lint speed** on a large JS/TS codebase matters most, Oxlint + Oxfmt is the fastest of the three. Pair it with Stylelint if you also need CSS linting.

See the individual provider pages ([Biome](/providers/biome), [ESLint](/providers/eslint), [Oxlint](/providers/oxlint)) for Ultracite-specific setup details.

---

# Migrate
Source: https://www.ultracite.ai/docs/migrate

Migrating to Ultracite means replacing your own lint and format configuration (the rules you picked for ESLint, Prettier, Stylelint, Biome or Oxlint) with Ultracite's presets. It doesn't mean giving up those tools: a project on ESLint can stay on ESLint, and one on Biome can stay on Biome. If you'd also like to change engines, see [Providers](/providers) to choose one, and pick it when `init` asks.

## Have Your Agent Do It

Paste this into Claude Code, Codex or another coding agent at the root of the project:

```text title="Prompt"
Migrate this project to Ultracite by following
https://www.ultracite.ai/docs/migrate.md. Keep the linter we use,
carry over our own rules that Ultracite's presets don't cover, and
migrate progressively, so the existing code passes today.
```

Every docs page is also served as Markdown at the same path with `.md` on the end, so the agent reads this page as plain text. The rest of it is written so an agent can follow it step by step.

## 1. Run Init

```package-install
npx ultracite@latest init
```

`init` preselects the linter it finds your config for. What it does with your existing configuration:

- **ESLint**: writes a flat config that spreads Ultracite's presets. An ES module config is updated in place, and a CommonJS one is replaced by `eslint.config.mjs`. Legacy `.eslintrc*` files stay, since ESLint 10 doesn't read them, so you can carry their rules over and delete them yourself. A config that doesn't use Ultracite's presets yet is replaced, with a warning naming the file, so its rules have to be carried over (step 2). Once it spreads an `ultracite/eslint/*` preset, re-running `init` keeps your additions.
- **Prettier** (with ESLint): writes a `prettier.config.mjs` that spreads Ultracite's settings. An ES module config is updated in place; a JSON, YAML, TOML or CommonJS config, or a `"prettier"` key in `package.json`, is replaced, with a warning.
- **Stylelint** (with ESLint): writes a `stylelint.config.mjs` that spreads Ultracite's config. A config that doesn't reference `ultracite/stylelint` is replaced, with a warning; one that builds on it and adds rules is left as it is.
- **Biome**: adds Ultracite's presets to the `extends` list of your `biome.json` or `biome.jsonc`, editing it in place, so your rules, settings and comments stay.
- **Oxlint**: adds Ultracite's presets to your `oxlint.config.ts`, keeping your own imports, `rules`, `overrides`, `ignorePatterns`, `jsPlugins` and `settings`. An `.oxlintrc.json` or `.oxfmtrc.json` is moved into the TypeScript configs and deleted, since Oxlint and Oxfmt refuse to run with two configs in one folder.

Moving to another engine removes the ESLint, Prettier and Stylelint packages Ultracite would have installed, and their config files, including legacy `.eslintrc*` files and the `"prettier"` and `"stylelint"` keys in `package.json`. An interactive run lists them and asks first; with `--yes`, `init` removes them without asking. If you keep them, `init` warns when `ultracite check` would still find and run the old linter. Packages in `dependencies` or `peerDependencies`, and plugins Ultracite doesn't install, stay. Oxlint doesn't lint CSS (Oxfmt only formats it), so pick Biome or ESLint if you rely on Stylelint.

`init` also merges your `.vscode/settings.json` rather than replacing it, adds `check` and `fix` scripts, and writes Ultracite's rules to `AGENTS.md`, so your agents write code that passes from the start. With type-aware linting, it also turns on `strictNullChecks` in your `tsconfig*.json` files unless one sets it to `false`, and an interactive run asks first. A config `init` can't parse is left unchanged, with a warning.

## 2. Carry Over Your Own Rules

Ultracite's presets cover most of what a typical config sets, so most of your old rules can go. Compare the old config (in Git, for example `git show HEAD:.eslintrc.json`) with the new one, and keep only what the presets don't do:

- Rules from plugins Ultracite doesn't include, and project-specific ones such as `no-restricted-imports` paths or naming conventions.
- Rules you turned off on purpose, with the reason in a comment.

Put them after Ultracite's presets, so they win. Leave out formatting rules: the formatter owns formatting now.

## 3. Format Everything in One Commit

```bash title="Terminal"
npx ultracite fix
```

This formats every file and applies the safe fixes. Commit it on its own, then add the commit's hash to a `.git-blame-ignore-revs` file, so `git blame` skips it. GitHub reads that file too.

## 4. Fix What's Left, or Migrate Progressively

`npx ultracite check` now reports what's left. On a small project, fix it in one go, with your agent doing the work:

```bash title="Terminal"
npx ultracite fix --claude
npx ultracite fix --codex
```

On a large codebase, it can be thousands of problems. Migrate progressively instead.

## Progressive Migration

Rather than fixing everything in one pull request, turn off the rules that fail today, then turn them back on a few at a time over the following weeks, fixing each batch as you go. The project passes from day one, new code follows every rule that's on, and the list of overrides is the migration's to-do list.

### Turn Off What Fails

List the rules that fail, then turn each one off after Ultracite's presets. Each engine shows them differently.

**Oxlint.** `npx ultracite check -f json` prints each problem with its rule as `plugin(rule)`. In `oxlint.config.ts` that's `plugin/rule`, except Oxlint's core rules, `eslint(rule)`, which are just `rule`:

```ts title="oxlint.config.ts"
export default defineConfig({
  env: core.env,
  extends: [core, react],
  ignorePatterns: core.ignorePatterns,
  // Progressive migration: remove a rule as its problems are fixed.
  rules: {
    "no-await-in-loop": "off",
    "typescript/no-explicit-any": "off",
    "unicorn/no-array-sort": "off",
  },
});
```

**Biome.** `npx ultracite check --reporter=summary` lists every rule with problems and how many. `lint/<group>/<rule>` goes under `linter.rules`, and `assist/source/<action>` under `assist.actions.source`:

```jsonc title="biome.jsonc"
{
  "extends": ["ultracite/biome/core", "ultracite/biome/react"],
  // Progressive migration: remove a rule as its problems are fixed.
  "linter": {
    "rules": {
      "performance": { "noAwaitInLoops": "off" },
      "suspicious": { "noExplicitAny": "off" },
    },
  },
  "assist": { "actions": { "source": { "useSortedKeys": "off" } } },
}
```

**ESLint.** ESLint can record every problem the code has today instead, so you don't need overrides:

```bash title="Terminal"
npx ultracite check --suppress-all
```

That writes `eslint-suppressions.json`, which you commit. The recorded errors stop failing `check`, but any new one fails, even in a file that already has some: the file records how many problems each rule has in each file, and when a file goes over, ESLint shows all of that rule's problems there. ESLint only suppresses errors, so warnings still show. Stylelint has no suppressions, so turn its failing rules off in `stylelint.config.mjs`, with `null`:

```js title="stylelint.config.mjs"
import ultracite from "ultracite/stylelint";

export default {
  ...ultracite,
  rules: {
    ...ultracite.rules,
    // Progressive migration: remove a rule as its problems are fixed.
    "selector-class-pattern": null,
  },
};
```

To keep a rule on for new files, turn it off only for the files that fail it today: in an Oxlint `overrides` entry with those `files`, or a Biome `overrides` entry with those `includes`.

### Turn Them Back On in Batches

Every week or two, pick a few overrides and remove them, one pull request each:

1. Remove the override, or for ESLint, start with one rule's suppressions: fix that rule's problems, then run `npx ultracite check --prune-suppressions` to drop the entries that no longer match anything.
2. Run `npx ultracite fix` to apply that rule's safe fixes, then `npx ultracite fix --claude` (or `--codex`) to have your agent fix the rest, one file at a time, each fix checked by re-running the linter.
3. Review and merge.

Start with the rules that have autofixes, which clear in one run, and with the ones that catch bugs, such as floating promises and unsafe `any`, before style rules. Your agent can run a whole batch from a prompt like:

```text title="Prompt"
Remove the "noAwaitInLoops" override from biome.jsonc, run
`npx ultracite fix`, then fix the problems that are left. Keep the
change to that one rule.
```

When the overrides are gone, or `eslint-suppressions.json` is empty, the migration is done.

## Without Init

To set Ultracite up by hand, install `ultracite` and your engine, then extend the `core` preset and the presets for your frameworks. Each [provider page](/providers) shows the config files `init` writes. Restart your editor afterwards, so it picks up the new configuration.

---

# Monorepos
Source: https://www.ultracite.ai/docs/monorepos

Ultracite is designed to work out of the box with monorepos. Here's how to use it with Turborepo.

## Configuration

When initializing Ultracite, it will create the appropriate config file(s) in the root of your repository based on your chosen linter. This configuration applies to your entire monorepo.

```
my-turborepo/
├── apps/
├── packages/
├── turbo.json
└── oxlint.config.ts + oxfmt.config.ts (or .mts, biome.jsonc, eslint.config.mjs, etc.)
```

## Different frameworks per workspace

When workspaces use different frameworks, scope each framework's rules to its workspace so, for example, React rules don't run on an Astro docs site. Pass `--workspace-framework <path>=<framework>` to `init` for each workspace and framework:

```bash title="Terminal"
npx ultracite init --frameworks vitest --workspace-framework apps/web=react apps/web=tanstack apps/docs=astro
```

`--frameworks` still applies to the whole repository. For each workspace, `init` writes a config in that directory that extends the root config and adds the workspace's presets, and installs what those presets need at the root. Editor extensions and the linters themselves read these configs too, so they report the same rules as `ultracite check`. Packages without a config of their own keep the root config.

`init` leaves a workspace config that already exists unchanged and tells you which presets to add. The configs it writes look like this, so you can also write or update them yourself.

### Oxlint

```ts title="apps/web/oxlint.config.ts"
import { defineConfig } from "oxlint";
import react from "ultracite/oxlint/react";
import tanstack from "ultracite/oxlint/tanstack";

import root from "../../oxlint.config.ts";

// Oxlint lints each file with its nearest config alone, so this extends the
// root config and repeats the properties that extends doesn't carry over.
export default defineConfig({
  env: root.env,
  extends: [root, react, tanstack],
  ignorePatterns: root.ignorePatterns,
  settings: root.settings,
});
```

Oxlint uses the config nearest each file instead of merging it with the root one. Extending the root config brings in its presets, rules and JS plugins, but not its `env`, `ignorePatterns` or `settings`, so the workspace config repeats them. In a workspace whose `package.json` doesn't set `"type": "module"`, the file is `oxlint.config.mts`.

### Biome

```jsonc title="apps/web/biome.jsonc"
{
  "$schema": "../../node_modules/@biomejs/biome/configuration_schema.json",
  "extends": [
    "ultracite/biome/core",
    "ultracite/biome/vitest",
    "../../biome.jsonc",
    "ultracite/biome/react",
    "ultracite/biome/tanstack",
  ],
  "root": false,
}
```

Biome's `"//"` shorthand inherits the whole root config but can't be combined with other `extends` entries. Extending the root config by path applies its own settings but not the presets it extends, so the workspace config lists the root's `extends` first. When you change the root config's `extends`, update the workspace configs to match.

### ESLint

```js title="apps/web/eslint.config.mjs"
/* eslint-disable import-x/no-extraneous-dependencies, import-x/no-relative-packages -- imports the presets and config of the root package */
import react from "ultracite/eslint/react";
import tanstack from "ultracite/eslint/tanstack";

import root from "../../eslint.config.mjs";

// ESLint lints each file with its nearest config alone, so this spreads the
// root config before the workspace's presets.
export default [...root, ...react, ...tanstack];
```

ESLint also uses the config nearest each file, so the workspace config spreads the root config before its presets. The presets come from the root package and the root config sits in another package, which core's `import-x` rules would flag. `init` disables only the rules that apply: none for a directory without its own `package.json`, and not `import-x/no-extraneous-dependencies` when the workspace lists `ultracite` as a dependency.

## Adding scripts

Because Ultracite's underlying tools are fast (especially the Rust-based Biome and Oxlint), you can run a single root script rather than creating separate scripts in each package.

`ultracite init` adds `check` and `fix` scripts to your root `package.json`. If you set Ultracite up by hand, add them yourself:

```json title="package.json"
{
  "scripts": {
    "check": "ultracite check",
    "fix": "ultracite fix"
  }
}
```

Optionally, add these as root tasks in your `turbo.json`:

```json title="turbo.json"
{
  "tasks": {
    "//#check": {},
    "//#fix": {
      "cache": false
    }
  }
}
```

You can now run `turbo run check` and `turbo run fix` from anywhere in your monorepo.

---

# Optional Presets
Source: https://www.ultracite.ai/docs/presets

Ultracite's core and framework presets are on when you run `init`. The presets on this page are opt-in: each adds rules that suit some projects and not others, and most run through Oxlint's JS plugin API, which is slower than Oxlint's native rules. The JS plugin, TSDoc, anti-slop and `@shadcn/lint` presets are for Oxlint; the gdp-ts preset works with Oxlint and ESLint.

## ESLint Parity

The core preset — and the `react`, `next`, and `tanstack` framework presets — run entirely on Oxlint's native, Rust-powered rules for maximum speed. If you want to close the remaining gap with the ESLint preset, Ultracite ships an opt-in `js-plugins` preset that runs [`eslint-plugin-github`](https://github.com/github/eslint-plugin-github), [`eslint-plugin-sonarjs`](https://github.com/SonarSource/eslint-plugin-sonarjs), and [`oxlint-plugin-react-doctor`](https://www.npmjs.com/package/oxlint-plugin-react-doctor) through Oxlint's JS plugin support. TSDoc syntax and public API documentation checks are available as separate, explicitly selected plugins below; they are not added to the full preset, so existing users do not gain new dependencies when upgrading.

This is **off by default** because it adds dependencies and runs a slower JavaScript lint pass instead of the native Rust one. You can enable it during setup: interactive `ultracite init` lets you choose individual JS plugins when you choose Oxlint, and non-interactive setup accepts package names via `--js-plugins`.

```package-install
npx ultracite init --linter oxlint --js-plugins eslint-plugin-github eslint-plugin-sonarjs oxlint-plugin-react-doctor
```

:::note
The React Doctor rules used to be bundled into the `react`, `next`, and `tanstack` presets. They now live in `js-plugins` so those framework presets stay on the fast native path. Extend `js-plugins` alongside your framework preset to keep them.
:::

React Doctor's framework-specific rules are split into per-framework add-on presets so they only run where they apply — `nextjs-*` rules like `nextjs-no-img-element` fire on plain `<img>`/`<a>` JSX and would false-positive in non-Next.js apps. `init` wires these up automatically when you pick the matching framework together with `oxlint-plugin-react-doctor`:

- `ultracite/oxlint/next/js-plugins` — React Doctor's Next.js rules
- `ultracite/oxlint/tanstack/js-plugins` — React Doctor's TanStack Query/Router/Start rules

If you're adding the preset manually instead of through `init`, install the plugins yourself:

```package-install
npm install -D eslint-plugin-github eslint-plugin-sonarjs oxlint-plugin-react-doctor
```

```ts title="oxlint.config.ts"
import { defineConfig } from "oxlint";
import core from "ultracite/oxlint/core";
import jsPlugins, { jsPluginSettings } from "ultracite/oxlint/js-plugins";

export default defineConfig({
  env: core.env,
  extends: [core, jsPlugins],
  ignorePatterns: core.ignorePatterns,
  jsPlugins: jsPlugins.jsPlugins,
  settings: jsPluginSettings,
});
```

:::note
`jsPlugins: jsPlugins.jsPlugins` re-declares the plugin packages on your root config. Oxlint already loads them from the extended preset, but dependency analyzers such as [Knip](https://knip.dev) only read `jsPlugins` from the root config and would otherwise report the packages as unused devDependencies. `ultracite init` emits this line for you.
:::

:::note
`settings: jsPluginSettings` must live on your root config — Oxlint does not merge `settings` from extended configs. It keeps React Doctor's ported rules (such as `only-export-components`) in their framework-aware "curated" mode, so Next.js route-segment exports like `export const dynamic = "force-static"` are not flagged as non-component exports.
:::

In a Next.js or TanStack app, add the matching add-on preset as well:

```ts title="oxlint.config.ts"
import { defineConfig } from "oxlint";
import core from "ultracite/oxlint/core";
import next from "ultracite/oxlint/next";
import jsPlugins, { jsPluginSettings } from "ultracite/oxlint/js-plugins";
import nextJsPlugins from "ultracite/oxlint/next/js-plugins";

export default defineConfig({
  env: core.env,
  extends: [core, next, jsPlugins, nextJsPlugins],
  ignorePatterns: core.ignorePatterns,
  jsPlugins: jsPlugins.jsPlugins,
  settings: jsPluginSettings,
});
```

### TSDoc and Public API Documentation

Two more JS plugins check the documentation in TypeScript files (`.ts`, `.tsx`, `.mts`, and `.cts`). They aren't part of the full `js-plugins` preset, so they only run when you select them:

- `eslint-plugin-tsdoc`, registered as `tsdoc`, validates [TSDoc](https://tsdoc.org) syntax.
- `eslint-plugin-jsdoc`, registered as `jsdoc-js` because Oxlint reserves `jsdoc` for its native plugin, requires a doc comment on every exported function, class, interface, type alias, and enum. It also covers the public methods and getters of exported classes, and exports that wrap a function, such as `export const Button = forwardRef(...)`.

Selecting `eslint-plugin-jsdoc` also turns on Oxlint's native `jsdoc/require-param` and `jsdoc/require-returns`, so every JSDoc comment on a function, exported or not, must describe its parameters and return value. Parameter and return types stay off, so TypeScript types aren't repeated in comments.

Selecting `eslint-plugin-tsdoc` adjusts core's native `jsdoc/*` rules to fit TSDoc: tags such as `@remarks` and `@typeParam` are allowed, and generators don't need `@yields`. With both plugins selected, a destructured parameter is documented by its own name (`@param props - ...`) rather than property by property. TSDoc has no `{Type}` syntax, so write the type on a `@throws` tag as a link: `@throws {@link RangeError} When the input is empty.`

```package-install
npx ultracite init --linter oxlint --js-plugins eslint-plugin-tsdoc eslint-plugin-jsdoc
```

`--js-plugins` sets the whole selection, so list any plugins you already use, such as `eslint-plugin-github`. A config that extends the full `js-plugins` preset keeps its plugins.

If you're configuring Oxlint manually, install the plugins and select them:

```package-install
npm install -D eslint-plugin-tsdoc eslint-plugin-jsdoc
```

```ts title="oxlint.config.ts"
import { defineConfig } from "oxlint";
import core from "ultracite/oxlint/core";
import { selectJsPlugins } from "ultracite/oxlint/js-plugins";

const jsPlugins = selectJsPlugins(["tsdoc", "jsdoc-js"]);

export default defineConfig({
  env: core.env,
  extends: [core, jsPlugins],
  ignorePatterns: core.ignorePatterns,
  jsPlugins: jsPlugins.jsPlugins,
});
```

## Anti-Slop Rules

Ultracite also ships an opt-in `anti-slop` preset built on [anti-slop](https://github.com/dmmulroy/anti-slop), Dillon Mulroy's set of opinionated Oxlint rules that reject low-evidence, low-signal TypeScript and JavaScript patterns — unjustified type assertions, `unknown` leaking through function signatures, `Reflect`-based property access, module mocking, and similar escape hatches.

Upstream is deliberately not published to npm (its distribution model is "copy the source into your repo"), so Ultracite vendors a self-contained bundled build of the plugin — there is nothing extra to install. Like `js-plugins`, this preset is **off by default** because it is strongly opinionated and runs through Oxlint's slower JS-plugin pass.

You can enable it during setup: it appears as `anti-slop` in the same JS-plugins prompt as the packages above, and non-interactive setup accepts it via `--js-plugins`:

```package-install
npx ultracite init --linter oxlint --js-plugins anti-slop
```

Or add it to your config manually:

```ts title="oxlint.config.ts"
import { defineConfig } from "oxlint";
import antiSlop from "ultracite/oxlint/anti-slop";
import core from "ultracite/oxlint/core";

export default defineConfig({
  env: core.env,
  extends: [core, antiSlop],
  ignorePatterns: core.ignorePatterns,
});
```

All eighteen rules are enabled at the `error` level, including `require-safety-comment-for-type-assertion` (every `as` assertion needs a `SAFETY:` comment stating the checked invariant), `no-unknown-returns` / `no-unknown-parameters` (parse values into named domain types at boundaries), `no-module-mocking` (inject dependencies instead of mocking modules), and `require-readable-spacing` (blank lines around top-level declarations, multiline bindings, control flow, returns, and blocks — a pattern AI-generated code tends to pack together; the fix only inserts whitespace, so `ultracite fix` restores the spacing without fighting the formatter). If a rule doesn't fit your codebase — `no-module-mocking` is a common example in test-heavy projects — turn it off in your own config's `rules` block.

## Design System Rules with @shadcn/lint

Ultracite also ships an opt-in `shadcn` preset built on [`@shadcn/lint`](https://github.com/shadcn-ui/lint), shadcn's agent-first linter for Tailwind v4 design systems. It reads your components, variants, and theme, and when a class breaks the design system the error explains what is wrong and what to use instead — the component's variants, sizes, theme tokens, and the file to edit. shadcn/ui is not required: it works with any Tailwind v4 component directory and theme.

Like `js-plugins`, this preset is **off by default** because it adds a dependency and runs through Oxlint's slower JS-plugin pass. You can enable it during setup: it appears as `@shadcn/lint` in the same JS-plugins prompt as the packages above, and non-interactive setup accepts it via `--js-plugins`:

```package-install
npx ultracite init --linter oxlint --js-plugins @shadcn/lint
```

Or add it to your config manually:

```package-install
npm install -D @shadcn/lint
```

```ts title="oxlint.config.ts"
import { defineConfig } from "oxlint";
import core from "ultracite/oxlint/core";
import shadcn from "ultracite/oxlint/shadcn";

export default defineConfig({
  env: core.env,
  extends: [core, shadcn],
  ignorePatterns: core.ignorePatterns,
  jsPlugins: shadcn.jsPlugins,
});
```

All six rules are enabled at the `error` level:

| Rule | What it catches |
| --- | --- |
| `no-restyle` | Restyling a design-system component through `className`. |
| `no-raw-colors` | Raw palette colors such as `bg-pink-500` and undeclared tokens. |
| `no-arbitrary-values` | Arbitrary values such as `p-[13px]` when a scale value exists. |
| `no-inline-styles` | Inline `style` props and `<style>` elements. |
| `no-unknown-classes` | Classes your Tailwind cannot generate, such as `rounded-huge`. |
| `require-static-classes` | Component class values the linter cannot read, such as `` `bg-${color}` ``. |

`no-restyle` and `no-arbitrary-values` use the upstream recommended `allow: ["layout"]` policy: pages may place a component (`mt-4`, `w-full`, `flex-1`, `absolute`) but its padding, colors, typography, and shape stay in the component's variants. The preset also turns `no-restyle`, `no-arbitrary-values`, and `require-static-classes` off inside `**/components/ui/**`, where components style themselves and call their own variant functions; `no-raw-colors`, `no-inline-styles`, and `no-unknown-classes` stay on there.

Components and the theme are discovered from `components.json`, or from `components/ui` / `src/components/ui` next to the nearest `package.json`. If your design system lives elsewhere, point the plugin at it with `settings.shadcn` on your root config — Oxlint does not merge `settings` from extended configs — and add a matching override for that directory:

```ts title="oxlint.config.ts"
export default defineConfig({
  env: core.env,
  extends: [core, shadcn],
  ignorePatterns: core.ignorePatterns,
  jsPlugins: shadcn.jsPlugins,
  settings: {
    shadcn: { ui: "@workspace/ui/components" },
  },
  overrides: [
    {
      files: ["packages/ui/src/components/**"],
      rules: {
        "shadcn/no-arbitrary-values": "off",
        "shadcn/no-restyle": "off",
        "shadcn/require-static-classes": "off",
      },
    },
  ],
});
```

Per-component policies (`contracts`), custom messages, and exceptions for external stylesheets are configured on the rules themselves — see the [`@shadcn/lint` documentation](https://github.com/shadcn-ui/lint/blob/main/docs/rules.md). `no-unknown-classes` asks your installed Tailwind v4 which classes exist; when Tailwind or the theme cannot be loaded it falls back to a bundled grammar and warns once.

## Authorization Proofs with gdp-ts

Ultracite also ships an opt-in `gdp` preset for [gdp-ts](https://github.com/rauchg/gdp-ts), a TypeScript take on Ghosts of Departed Proofs. Sensitive functions demand a proof about their exact arguments (`UserIsProjectAdmin<U, P>`) that only a trusted module in `proofs/` can mint, so a skipped or mismatched authorization check is a compile error. TypeScript can't stop a proof being forged with `{} as UserIsProjectAdmin<U, P>`; these rules close that gap.

The lint plugin ships inside `@gdp-ts/core`, so once your codebase uses gdp-ts there is nothing extra to install. Add the preset after core:

```ts title="oxlint.config.ts"
import { defineConfig } from "oxlint";
import core from "ultracite/oxlint/core";
import gdp from "ultracite/oxlint/gdp";

export default defineConfig({
  env: core.env,
  extends: [core, gdp],
  ignorePatterns: core.ignorePatterns,
});
```

The preset follows upstream's strict mode:

| Rule | Applies | What it catches |
| --- | --- | --- |
| `gdp-ts/no-define-proof` | outside `proofs/` | Importing or calling `defineProof` to mint a proof outside a trusted module. |
| `gdp-ts/no-proof-assertion` | outside `proofs/` | Type assertions to `Named`, `Proof`, or any type imported from a `proofs` path. |
| `gdp-ts/no-type-assertion` | outside `proofs/` and `lib/ids.ts` | Every other type assertion except `as const`. The honest path never needs one. |
| `gdp-ts/no-exported-prover` | inside `proofs/` | Exporting a prover, which would let any module mint the proof. |

Upstream's strict-mode `no-any` is left off because core's `typescript/no-explicit-any` already bans `any` everywhere. Inside `proofs/`, `typescript/no-empty-interface` and `typescript/no-empty-object-type` allow an empty interface that extends a single type, which is how gdp-ts declares a proof (`interface UserIsProjectAdmin<U, P> extends Proof<"UserIsProjectAdmin", [U, P]> {}`). Core's `no-redeclare` stays on, so give the prover its own name (`const prover = defineProof("UserIsProjectAdmin")`) instead of reusing the proof interface's name as the upstream recipe does.

The preset follows the upstream layout: trusted modules in `proofs/` and branded-id constructors in `lib/ids.ts`. For a different layout, add overrides with the same shape in your own config.

### On ESLint

The same preset ships for ESLint. Spread it after core:

```javascript title="eslint.config.mjs"
import core from "ultracite/eslint/core";
import gdp from "ultracite/eslint/gdp";

export default [...core, ...gdp];
```

It matches the Oxlint preset: upstream's strict mode stops proofs being forged with type assertions or minted outside `proofs/`, and empty proof interfaces (`interface X<P> extends Proof<"X", [P]> {}`) are allowed inside `proofs/`. It also sets `@typescript-eslint/no-unused-vars` to ignore `_`-prefixed arguments, as Oxlint does by default, because sensitive functions take proofs they never read at runtime (`_proof: UserIsProjectAdmin<U, P>`).

---

# Setup
Source: https://www.ultracite.ai/docs/setup

Ultracite can be installed with all major package managers. You'll need Node.js 22.18 or later (or Bun) and a project with a `package.json` file. If you're new to Ultracite, the [introduction](/docs) covers what it is and which toolchains it supports.

## Installation

The easiest way to get started is to run Ultracite's `init` script, which will install the necessary packages and set up the config files for you. In your project directory, run:

```package-install
npx ultracite init
```

You can optionally pass the following flags to the `init` command:

| Flag | Description | Options |
| --- | --- | --- |
| `--linter` | The linting toolchain to use. When omitted and prompts are skipped, init keeps the linter the project already uses, or picks `oxlint` for a project without one. | `oxlint`, `biome`, `eslint` |
| `--pm` | The package manager to use. | `pnpm`, `bun`, `yarn`, `npm`, `deno`, `nub`, `aube` |
| `--frameworks` | The frameworks to configure. | Space-separated: `react`, `next`, `solid`, `vue`, `svelte`, `qwik`, `remix`, `tanstack`, `angular`, `astro`, `nestjs`, `jest`, `vitest`, `cypress`, `storybook` |
| `--workspace-framework` | Frameworks for one workspace of a monorepo, as `<path>=<framework>`. Writes a config in that workspace that extends the root config. See [Monorepos](/docs/monorepos#different-frameworks-per-workspace). | Space-separated: `apps/web=react`, `apps/docs=astro` |
| `--editors` | The editors to configure. | Space-separated: `universal`, `vscode`, `cursor`, `devin`, `antigravity`, `kiro`, `trae`, `void`, `bob`, `codebuddy`, `zed`. Use `universal` to write `.vscode/settings.json` for every VS Code-based editor. |
| `--agents` | The AI agents to configure. | Space-separated: `universal`, `claude`, `codex`, `jules`, `replit`, `devin`, `lovable`, `zencoder`, `ona`, `openclaw`, `snowflake-coco`, `deepagents`, `qoder`, `kimi-code`, `xum`, `pi`, `adal`, `copilot`, `cline`, `amp`, `aider`, `open-hands`, `gemini`, `junie`, `augmentcode`, `bob`, `kilo-code`, `goose`, `warp`, `droid`, `opencode`, `crush`, `qwen`, `kiro-cli`, `firebender`, `cursor-cli`, `mistral-vibe`, `vercel`, `fx`, `antigravity`, `grok` |
| `--hooks` | The agent hooks to configure. | Space-separated: `cursor`, `devin`, `codebuddy`, `claude`, `codex`, `deepagents`, `copilot`, `grok` |
| `--integrations` | Additional integrations to set up. | Space-separated: `husky`, `lefthook`, `lint-staged`, `pre-commit` |
| `--install-skill` | Install the reusable Ultracite skill after setup. | (no value needed) |
| `--js-plugins` | Optional Oxlint JS plugins to enable. Only Oxlint runs them, so without `--linter`, init skips the linter prompt and keeps the project's linter (or picks `oxlint`), and stops if that linter isn't Oxlint. | Space-separated: `@shadcn/lint`, `anti-slop`, `eslint-plugin-github`, `eslint-plugin-jsdoc`, `eslint-plugin-sonarjs`, `eslint-plugin-tsdoc`, `oxlint-plugin-react-doctor` |
| `--type-aware` | Turn on type-aware linting: the rules that need type information or a scan of the whole project. Adds `ultracite/eslint/type-aware` for ESLint and `ultracite/biome/type-aware` for Biome; for Oxlint, installs `oxlint-tsgolint` and sets `typeAware` in the config. Also turns on `strictNullChecks` in your tsconfig files, which those rules need. Without the flag, an interactive run asks. | (no value needed) |
| `--skip-install` | Skip installing dependencies. | (no value needed) |
| `--yes`, `-y` | Take the default for every question no flag answers, without prompting. | (no value needed, on automatically in CI and when there's no terminal) |
| `--quiet` | Only print warnings and errors. | (no value needed) |

Every prompt, including the skill one, is skipped when you pass `--yes` or any of `--pm`, `--editors`, `--agents`, `--hooks`, `--integrations`, `--frameworks`, or `--workspace-framework`. Whatever those flags leave out takes its default: no editors, agents, hooks, or integrations, and no skill unless you pass `--install-skill`. So you can re-run `init` with just `--hooks` or `--agents` to add those to a project without changing its linter. In the interactive prompt, the linter the project already uses is preselected.

`init` asks every question before it changes anything. When you pick a different linter, an interactive run lists the other linters' config files and packages and asks before removing them; if you keep them, `ultracite check` may still find and run the old linter. When type-aware linting is on, it also lists the tsconfig files that don't have `strictNullChecks` yet and asks before turning it on. `--yes` does both without asking. An ESLint setup keeps legacy `.eslintrc` files, which ESLint 10 doesn't read.

`init` checks every flag value before it changes anything. An unknown value (for example, `--linter eslnt`) stops it with a list of the valid values, and `--js-plugins` with `--linter biome` or `--linter eslint` stops it too. `--agents` is the exception: an agent ID `init` doesn't know gets `AGENTS.md`, which most agents read, and a warning. The old IDs of renamed agents and editors (`amazon-q-cli`, `mux`, `kimi-cli`, `snowflake-cortex` and `windsurf`) still work, with a note to switch to the new one.

### Programmatic Usage

For tools that need to call Ultracite programmatically (like scaffolding CLIs), pass `--yes` to skip the prompts and `--quiet` to drop the progress output:

```bash title="Terminal"
npx ultracite init --yes --quiet --pm npm
```

`init` takes the defaults on its own when the `CI` environment variable is `true` or `1`, or when there's no terminal to answer prompts in, so it never waits for input in a pipeline:

```bash title="Terminal"
CI=true npx ultracite init --pm npm
```

With `--yes`, Ultracite will:

- Skip all interactive prompts
- Keep the project's current linter, or use Oxlint + Oxfmt for a project without one
- Remove other linters' configs and packages, and turn on `strictNullChecks` when type-aware linting is on, without asking
- Only set up editors, agents, hooks, Git hooks, and the skill when you pass their flags
- Exit with code 0 on success or 1 on failure

With `--quiet`, it leaves out the intro banner, spinners, and progress messages. Warnings, such as a config file it couldn't update, and errors still print.

You can combine `--yes` with `--linter` to specify a toolchain:

```bash title="Terminal"
npx ultracite init --yes --linter eslint --pm npm
```

### Editor Extensions

When `init` creates `.vscode/settings.json`, it installs the extension your linter needs: the Oxc extension for Oxlint, the Biome extension for Biome, or the ESLint and Prettier extensions for ESLint. It installs them with your editor's own command-line launcher (`code`, `cursor`, `devin-desktop` or `windsurf`, `buddy` for CodeBuddy, `antigravity-ide`, `bobide` for IBM Bob, `kiro`, `trae` or `void`), so they land in the editor you picked. Install them yourself from the editor's Extensions view if the settings file already existed, the launcher isn't on your `PATH`, or the install failed or took more than two minutes. The Stylelint extension is never installed for you. For VS Code (use your editor's launcher in place of `code`):

```bash title="Terminal"
# Oxlint + Oxfmt
code --install-extension oxc.oxc-vscode

# Biome
code --install-extension biomejs.biome

# ESLint + Prettier + Stylelint
code --install-extension dbaeumer.vscode-eslint
code --install-extension esbenp.prettier-vscode
code --install-extension stylelint.vscode-stylelint
```

Each editor has its own page, with the settings `init` writes for it and what to do after: see [Editors](/editors).

### Usage with Tailwind CSS

If you use Tailwind CSS, it's recommended to install the [Tailwind CSS IntelliSense](https://marketplace.visualstudio.com/items?itemName=bradlc.vscode-tailwindcss) extension for class sorting and hints:

```bash title="Terminal"
code --install-extension bradlc.vscode-tailwindcss
```

---

# Troubleshooting
Source: https://www.ultracite.ai/docs/troubleshooting

Even though Ultracite aims to simplify linting and formatting, you might encounter some issues during setup and usage. Here are some common issues and their solutions:

## "Ultracite isn't formatting on save in VS Code."

Double-check that you have the appropriate VS Code extension installed and enabled for your chosen linter (Biome, ESLint, or Oxlint). Verify your `.vscode/settings.json` contains the correct `editor.defaultFormatter` and `editor.codeActionsOnSave` entries generated by Ultracite.

Also ensure there's no conflicting formatter or linter extension enabled. If you have multiple formatting extensions active, they might interfere or take precedence over each other.

You may need to disable VS Code's built-in Format On Save if another formatter is grabbing the file. Try running the "Format Document" command manually and see if the correct formatter is used or if any error appears.

## "Found an unknown key `...`" / "Biome exited because the configuration resulted in errors."

Your linter is older than the Ultracite release you're on. Each Ultracite release enables rules from a specific linter version, and Biome, ESLint and Oxlint all reject a config that names a rule they don't have yet — so bumping `ultracite` without bumping the linter fails on the next `check` or `fix`. ESLint reports this as `Definition for rule '...' was not found` or a plugin load error; Oxlint as an unknown rule or plugin.

Run the upgrade command, which installs the linter versions the current release was verified with:

```bash title="Terminal"
npx ultracite upgrade
```

`npx ultracite doctor` reports the same mismatch (as a failed version check) without changing anything. Ultracite also declares these versions as optional peer dependencies, so your package manager warns on install when they drift.

If the versions already line up, the stale rule usually comes from your own overrides — check your `biome.jsonc` (or ESLint/Oxlint config) for a rule that was renamed or moved between linter releases.

## "I installed Ultracite, but VS Code still uses my old linter."

Ensure you removed or turned off your old configs. For example, if you have leftover `.eslintrc`, `.prettierrc`, or `biome.jsonc` files from a previous setup, VS Code extensions might still pick them up and cause duplicate diagnostics.

It's recommended to remove those configs (or at least disable the corresponding extensions) when switching linters to avoid confusion. Also check `.vscode/settings.json`: `init` merges its settings into the existing file, so a default formatter or code action from your previous linter can remain there. Let your chosen Ultracite toolchain take over as the sole linter/formatter.

## "Ultracite is throwing parse errors for files I don't want it to check."

A common example is installing components from a UI library like [`shadcn/ui`](https://ui.shadcn.com/). While they're designed to be modified, you may want to preserve the original source code for updates. In this case, you'll want to exclude those files from linting.

For Biome, add patterns to your `biome.jsonc`:

```jsonc title="biome.jsonc"
{
  "files": {
    "includes": ["**", "!components/ui/**", "!lib/**", "!hooks/**"],
  },
}
```

**Important:** You must include `"**"` as the first entry when using negated patterns in `files.includes`. Ultracite's base config sets `files.includes` to match all files (with its own exclusions). If you override `files.includes` with only negated patterns (e.g. `["!components/ui/**"]`), Biome will match zero files because there's no positive glob to start from. Always lead with `"**"` to include everything, then negate what you want to exclude.

By default, all linters should ignore `node_modules`, but if you opened a file manually from there, the extension might still try to lint it. Generally, ignore generated files or third-party code.

Another cause could be experimental syntax that your linter can't parse yet. Check your linter's issue tracker for support of that syntax.

## "I see double errors for the same issue."

This can happen if you have multiple linters running at once. It can also occur if VS Code's TypeScript checker and your linter both report the same error.

To resolve, standardize on one tool per type of check. If using Ultracite, disable other linters. For TypeScript type errors, VS Code's built-in TS server will show them (red squiggles for type issues) — your linter may also show type-driven lint issues. Usually this is fine as they highlight the same problem.

If it bothers you, you can turn off VS Code's TS validator (`"typescript.validate.enable": false` in settings), or vice versa. Just ensure you don't have two linters with overlapping functionality enabled.

## "Pre-commit hook/CI is failing due to Ultracite."

If your pre-commit hook fails, it means Ultracite found issues that couldn't be auto-fixed (the generated hooks run `ultracite fix`, which fixes what it can and fails on the rest). Run `ultracite fix` locally to auto-fix what can be fixed, then inspect the remaining output.

Address any remaining issues manually, then commit. If CI is failing on `ultracite check`, do the same: run it locally to see what issues were found. Treat Ultracite failures like failing tests — something to correct in code.

## "I get an error about `strictNullChecks` or type issues after enabling Ultracite."

Ultracite expects TypeScript strictness. If you haven't enabled `strictNullChecks` (or full `strict` mode), you might get TypeScript-related lint warnings about potential undefined usage that TS isn't catching due to loose settings.

The solution is to enable strict flags in your `tsconfig.json` as recommended. If you cannot do this for legacy reasons, you may need to disable certain rules that assume strictness. However, it's highly recommended to use TS strict mode — it improves code quality and aligns with Ultracite's philosophy.

## "Ultracite is too strict for our team — can I tone it down?"

Yes. While Ultracite's value is in being strict, you're free to override rules. If developers are overwhelmed by warnings, identify which rules are causing friction and turn them to `warn` or `off` in your config.

For instance, if you find the accessibility rules too noisy for an internal tool, you might disable some of them. Or if you disagree with a code style enforced, you can adjust it.

The key is communication with the team — perhaps educate why a rule exists before disabling it. If still unwanted, customize the config. Check out the [Configuration](/docs/configuration) section for more information on how to override rules.

## "Are there known limitations I should be aware of?"

Each linter has different coverage:

- **Biome** handles JS/TS/JSX/TSX/JSON/CSS/GraphQL but doesn't have every rule from ESLint's plugin ecosystem.
- **ESLint + Prettier + Stylelint** has the most comprehensive rule coverage with 20+ plugins, but is slower.
- **Oxlint** is the fastest but focuses on bug-catching rules over stylistic ones.

If your project relies on specific rules from a particular ecosystem (like certain Stylelint CSS checks or ESLint plugins), make sure your chosen linter supports them or consider using that toolchain instead.

---

If you run into an issue not covered here, check [Ultracite's GitHub issues](https://github.com/haydenbleasel/ultracite/issues) or the documentation for your chosen linter.

---

# Upgrade
Source: https://www.ultracite.ai/docs/upgrade

Ultracite's presets are pinned to specific linter releases, so bumping `ultracite` on its own can leave the linter behind, and a major release can change how your configuration should look. The `upgrade` command handles both:

```bash title="Terminal"
npx ultracite@latest upgrade
```

Use `@latest` the first time. `npx ultracite` runs the copy installed in your project, and releases before 8.0 don't have the options on this page.

## What It Does

1. Installs the latest `ultracite` release, or the one `--version` names, and prints a link to the release notes between your previous and new versions.
2. Hands off to the freshly installed CLI, so the rest of the upgrade uses the versions that release was verified with rather than the ones baked into the older copy.
3. Reinstalls your toolchain at those versions: Biome; ESLint, Prettier, Stylelint, and the plugins for every Ultracite preset your `eslint.config.*` imports (installing any that are missing); or Oxlint and Oxfmt. Optional extras you've already opted into (other framework plugins, Oxlint JS plugins, `oxlint-tsgolint`) are bumped too; ones you never installed are left alone.
4. Checks your configuration for the changes each major release made, and has your coding agent make the ones it still needs when you pass `--claude` or `--codex`.
5. Runs the same diagnostics as `doctor`, and exits non-zero if anything still fails or a change the agent was asked to make is missing.

## Let Your Coding Agent Update the Configuration

Major releases change what your configuration looks like: v8 took Prettier out of ESLint and Stylelint and moved ESLint's Cypress, Storybook and type-checked rules into presets of their own, v7 moved the Biome presets under `ultracite/biome/` and removed the `lint` and `format` commands, and v6 split the single preset into one per framework. Pass `--claude` or `--codex`, and Ultracite hands the changes your project still needs to that agent's CLI:

```bash title="Terminal"
npx ultracite@latest upgrade --claude
npx ultracite@latest upgrade --codex
```

The agent gets the upgrade guide for each release your configuration predates, oldest first, and changes only what they describe: linter configs, `package.json` scripts, Git hook and lint-staged configs, and CI workflows. It doesn't install packages or move you to another linter. It runs the way it does for [`fix --claude`](/docs/usage#ai-powered-fixing): Claude Code limited to reading and editing files, Codex in its workspace-write sandbox, with a 5-minute budget. Afterwards, Ultracite checks your project again, so what counts as done is what the files now say.

`--claude` needs the [Claude Code CLI](https://claude.com/claude-code) and `--codex` the [Codex CLI](https://github.com/openai/codex), installed and signed in. Ultracite checks for the CLI before it installs anything.

Ultracite decides which guides apply from your project rather than from the version you came from, so a project that skipped a major release, or had `ultracite` bumped by hand, still gets every change it's missing.

### Without an Agent

Without `--claude` or `--codex`, `upgrade` lists the guides your project still needs. They ship with Ultracite in `node_modules/ultracite/skills/ultracite/references/upgrades/`, and with the [Ultracite skill](/docs/ai/skills), so an agent that has the skill can follow them when you ask it to upgrade.

| Release | What changes |
| --- | --- |
| v8 | `prettier/prettier` overrides come out of ESLint and Stylelint configs, ESLint projects that use Cypress or Storybook import `ultracite/eslint/cypress` or `ultracite/eslint/storybook`, ESLint configs that set a type-checked rule import `ultracite/eslint/type-aware` and the framework add-ons, Oxlint projects with `oxlint-tsgolint` set `typeAware: true`, Zed formats with Prettier rather than ESLint's language server, and `ultracite init --quiet` gains `--yes`. |
| v7 | Biome presets move from `ultracite/<preset>` to `ultracite/biome/<preset>`, and `ultracite lint` and `ultracite format` become `ultracite check` and `ultracite fix`. |
| v6 | The single `ultracite` Biome preset splits into `ultracite/core` plus a preset for each framework. |
| v5 | Biome 2's configuration format replaces Biome 1's. |

Between major releases your configuration keeps working as it is. When the release notes call out preset changes, re-run `npx ultracite init` to regenerate Ultracite's parts of your configuration; it keeps your own additions.

## Upgrading to a Specific Release

`--version` takes a major version, a full version or a dist-tag:

```bash title="Terminal"
npx ultracite@latest upgrade --version 7
```

`--version 7` installs the newest 7.x release, so you can stay on one major after the next is out. `--claude` and `--codex` need 8 or later, since earlier releases can't hand the upgrade to an agent.

## Options

| Option | Description |
| --- | --- |
| `--version <version>` | The release to upgrade to, such as `7` or `7.12.4`. Defaults to `latest`. |
| `--claude` | Have the Claude Code CLI make the configuration changes the release needs. |
| `--codex` | Have the Codex CLI make the configuration changes the release needs. |
| `--pm <pm>` | The package manager to use, when it can't be detected from a lockfile. |

---

# Usage
Source: https://www.ultracite.ai/docs/usage

## IDE Integration

Ultracite works best when integrated into your editor, so you get immediate feedback as you write code. It is designed to run automatically on save.

To test it out, open a project in your IDE. As you edit files, you should see formatting take effect on save. Try introducing a small code style mistake (like an extra semicolon or a wrongly indented line) and hit Save — Ultracite will instantly reformat the file.

If you introduce a lint issue (like an unused variable), you'll see a squiggly underline or a warning in the Problems panel. On save, Ultracite will attempt to fix it if it's auto-fixable (for example, removing an unused import) or otherwise leave a warning for you to address.

### Instant formatting

Every time you save a file, your chosen linter formats the code. You don't need to run a separate formatter or worry about style — it's taken care of.

Thanks to the `codeActionsOnSave` settings, VS Code will also apply "fix all" actions on save. This means any lint rule with an auto-fix (like converting `!=` to `!==`, adding missing parentheses, fixing import order, etc.) will be applied automatically.

We also enable `formatOnPaste` — so if you paste code from elsewhere, it will immediately be formatted to match your style.

The key advantage is instant feedback. You write code, and Ultracite continuously keeps it clean. Over time, you'll spend little to no time fixing lint errors — Ultracite either fixes them for you or points them out early.

### Problems panel integration

Any issues that require your attention will show up in the Problems panel. For example, if Ultracite finds an error it can't fix (like a deprecated API or an unhandled Promise rejection), it will list it as an error or warning. Click it to jump to the location in code.

### Quick fixes

In many cases, the VS Code extension for your linter provides quick fix suggestions. If you see a yellow lightbulb or a suggestion popup, you can apply fixes manually as well.

## CLI Usage

Ultracite comes with a CLI that wraps your chosen linter. The commands work the same regardless of which toolchain you're using.

Any unknown flags are passed through to the underlying linter, so you can use any flag your linter supports (e.g. `--max-warnings` for ESLint, `--since` for Biome), and flags that take a value keep it (e.g. `--tsconfig tsconfig.json` or `--only lint/suspicious/noDebugger`). If you need to lint a file path that starts with `-`, pass it after `--` so Ultracite treats it as a file instead of a linter flag.

Both `check` and `fix` accept any file paths: files your tools don't handle, like a `Dockerfile`, `.env`, or `README`, are skipped rather than failing the run, so you can pass a list of changed files as is. With the ESLint toolchain, a missing Stylelint install skips CSS linting with a warning instead of stopping the other tools.

### Checking Code

The `check` command runs the linter without modifying files:

```bash title="Terminal"
npx ultracite check
```

### Fixing Code

The `fix` command runs the linter and auto-fixes issues:

```bash title="Terminal"
npx ultracite fix
```

You can also apply unsafe fixes (fixes that may change code behavior):

```bash title="Terminal"
npx ultracite fix --unsafe
```

With Biome, this applies Biome's unsafe fixes; with Oxlint, it runs `oxlint --fix-dangerously`. ESLint has no unsafe tier of fixes, so with the ESLint toolchain the flag is ignored with a warning.

Some Biome fixes are intentionally marked unsafe because they can change runtime behavior. For example, Ultracite already enables Biome's `noSubstr` rule, but rewriting `substring()` or `substr()` to `slice()` only happens when you run `ultracite fix --unsafe`.

### AI-Powered Fixing

The `--claude` and `--codex` flags hand any issues that survive the autofix pass to a local agent CLI, which repairs them autonomously — file by file, with a live per-issue status line that flips to ✓ once the fix is verified:

```bash title="Terminal"
npx ultracite fix --claude
npx ultracite fix --codex
```

The flow: Ultracite runs its normal autofix pass, collects the remaining (unfixable) diagnostics, and then invokes the agent once per affected file with the full, untruncated diagnostics — including rule help text and documentation URLs. After each agent run, Ultracite re-lints the file and only marks an issue fixed if the diagnostic actually cleared. If any diagnostics survive, the agent gets up to two more attempts on that file, each with the fresh post-edit diagnostics and explicit feedback that the previous approach failed — so a superficial edit that dodges the symptom rather than the rule gets caught and retried instead of reported as fixed. The command exits non-zero if any issues remain, matching the plain `fix` contract.

Requirements and behavior:

- `--claude` requires the [Claude Code CLI](https://claude.com/claude-code) (`npm install -g @anthropic-ai/claude-code`); `--codex` requires the [Codex CLI](https://github.com/openai/codex) (`npm install -g @openai/codex`). Both must be authenticated.
- Agents run non-interactively with scoped permissions: Claude Code uses `claude -p --permission-mode acceptEdits` limited to read/edit tools (no shell access), and Codex runs in its workspace-write sandbox via `codex exec --sandbox workspace-write --skip-git-repo-check`, so it also works in a project that isn't a Git repository. The prompt is sent on stdin.
- Each agent attempt gets a 5-minute budget, and the re-lint decides the outcome either way — even a failed or timed-out run gets credit for diagnostics it managed to clear. Whatever remains unfixed after the attempts is marked ✗ and the run continues with the next file.
- Other flags combine as usual, e.g. `npx ultracite fix --claude --unsafe`.

### Type-Aware Linting

Type-aware linting adds rules that use TypeScript's type system or a scan of the whole project. It's off unless you ask for it, since it makes linting slower. Pass `--type-aware` to `ultracite init` (an interactive run asks in a TypeScript project), and init sets it up for your linter and turns on `strictNullChecks` in your tsconfig files, which these rules need. It lists the tsconfig files and asks first, unless you pass `--yes`.

#### Biome

For Biome, `--type-aware` adds the `ultracite/biome/type-aware` preset to your Biome config's `extends` array. This enables the project/scanner rules `noPrivateImports`, `noUnresolvedImports`, `noImportCycles`, `noDeprecatedImports`, `useJsonImportAttributes`, and `useArraySortCompare`.

```bash title="Terminal"
npx ultracite init --linter biome --type-aware
```

Since the rules are baked into your Biome config, they work in both the CLI and your IDE automatically — no runtime flags needed.

#### ESLint

For ESLint, `--type-aware` adds `ultracite/eslint/type-aware` to `eslint.config.mjs`, plus the type-aware add-on of each framework preset that has one. It turns on the typescript-eslint, SonarJS and Unicorn rules that need type information, such as `no-floating-promises` and `no-misused-promises`, through `projectService`, which finds the `tsconfig.json` that includes each file. Without it, ESLint lints TypeScript without type information and needs no tsconfig.

```bash title="Terminal"
npx ultracite init --linter eslint --type-aware
```

#### Oxlint

For Oxlint, `--type-aware` installs `oxlint-tsgolint` and sets `options: { typeAware: true }` in `oxlint.config.ts`, so `ultracite check`, `ultracite fix` and the editor extension all run rules like `no-floating-promises`, `no-misused-promises`, and `await-thenable` that catch bugs by analyzing types.

```bash title="Terminal"
npx ultracite init --linter oxlint --type-aware
```

You can also enable TypeScript compiler diagnostics (experimental) at runtime:

```bash title="Terminal"
npx ultracite check --type-check
npx ultracite fix --type-check
```

:::note
`--type-check` is an Oxlint flag, passed through to Oxlint. Type-aware rules are set up in the config at init time on every linter and need no runtime flag.
:::

### Validating Setup

The `doctor` command checks your setup for issues and provides recommendations. This is useful to run after installing Ultracite to ensure everything is configured correctly:

```bash title="Terminal"
npx ultracite doctor
```

Alongside the config checks, `doctor` compares the linter and formatter installed in your project against the versions this Ultracite release was verified with — Biome, ESLint, Prettier and Stylelint, or Oxlint and Oxfmt. A tool that is too old fails the check, because the presets reference rules it doesn't know about yet (the `Found an unknown key` crash). A tool that is newer than the supported range only warns.

For Oxlint projects, `doctor` also fails when two Oxlint or two Oxfmt configs sit in the same directory (for example, `.oxlintrc.json` next to `oxlint.config.ts`), since the tools refuse to load either, and when an `oxlint.config.ts` or `oxfmt.config.ts` is in a `"type": "commonjs"` package, where Node can't load it. Re-running `npx ultracite init` fixes both. Under Yarn Plug'n'Play, where packages aren't in `node_modules`, `doctor` warns instead of failing when it can't confirm Ultracite is installed or read a tool's version.

### Upgrading

`npx ultracite@latest upgrade` installs the latest release and reinstalls your linter at the versions it was verified with. Pass `--claude` or `--codex` to have that agent bring your configuration up to date with the release. See [Upgrade](/docs/upgrade).