Migrate Oxfmt

This walks you through switching from Prettier or Biome to Oxfmt, a faster formatter that's mostly Prettier-compatible. It runs an automated migration command that converts your config file and ignore patterns, then explains what to review afterward. The main gotchas are printWidth defaults (80 vs 100), overrides that need manual conversion, and a few experimental Prettier features that don't work yet. It also covers oxfmt-specific extensions like import sorting and Tailwind class ordering. Useful if you want the speed bump without rewriting all your formatting rules by hand, though you'll still need to spot-check the output and handle edge cases yourself.

skills.sh installs: 4.3K
GitHub stars: 23.4K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add oxc-project/oxc --skill migrate-oxfmt --agent claude-code

Installs into .claude/skills of the current project.

Files

This skill guides you through migrating a project from Prettier or Biome to Oxfmt.

Overview

Oxfmt is a high-performance, Prettier-compatible code formatter. Most Prettier options are supported directly.

An automated migration tool is built into Oxfmt, supporting both Prettier and Biome as migration sources.

Step 1: Run Automated Migration

First, decide whether the automated tool fits:

Static config (JSON, or a JS/TS config that just exports a plain object): use --migrate below.
Dynamic JS/TS config (logic such as environment branches or computed values): --migrate writes only a resolved snapshot of the values, and the logic does not survive (a warning is printed). Port the logic to oxfmt.config.ts manually with the option mappings in this guide.
Nested per-directory configs: --migrate only handles the config in the current directory. Run it again in each nested directory (see "Nested Config" in Step 2).