migrate-oxfmt

Migrate Prettier or Biome configs to Oxfmt .oxfmtrc.json.

512|47|Updated Apr 7, 2021
One-click install
npx skills add https://github.com/dxos/dxos --skill migrate-oxfmt-dxos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-oxfmt
Source: https://github.com/dxos/dxos/tree/main/.agents/skills/migrate-oxfmt
Command: npx skills add https://github.com/dxos/dxos --skill migrate-oxfmt-dxos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating JavaScript/TypeScript projects from Prettier or Biome to Oxfmt, aligning formatting tooling across teams to reduce fragmentation and confusion.

Core Features & Use Cases

  • Automated migration of Prettier and Biome configurations to Oxfmt, including creating .oxfmtrc.json with migrated options.
  • Migration of ignore patterns and relevant plugin mappings (e.g., tailwind or package.json handling) from source configs to Oxfmt equivalents.
  • Guidance on handling edge cases (missing source config, existing .oxfmtrc.json, or manual adjustments for unsupported options).

Quick Start

Run the automated migration to generate an Oxfmt configuration for your project from Prettier or Biome configurations.

Frequently Asked Questions about migrate-oxfmt

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

FAQPage Schema
How do I migrate my Prettier config to Oxfmt?

The Skill reads your existing Prettier configuration, converts supported formatting options, migrates ignore patterns, and generates a new .oxfmtrc.json file for your JavaScript or TypeScript project.

Can I migrate a Biome configuration to Oxfmt?

Yes, the Skill reads your biome.json or biome.jsonc file, translates relevant formatting options and ignore patterns, and outputs an equivalent .oxfmtrc.json configuration for your project.

What happens to unsupported Prettier or Biome options during migration?

The migration automatically converts supported fields to .oxfmtrc.json and explicitly flags unsupported options, noting manual adjustments needed for fields that cannot be automatically mapped.

How does the migration handle existing Oxfmt configurations?

When an existing .oxfmtrc.json is present, the Skill provides guidance on handling this edge case to prevent overwriting, managing configuration conflicts safely during the transition.

Does the migration support Prettier plugin options like Tailwind?

Yes, the Skill translates relevant plugin mappings such as Tailwind and package.json handling into their appropriate Oxfmt equivalents within the generated .oxfmtrc.json file.