Biome formatter for JS/TS/JSON/CSS — the modern Prettier/ESLint replacement. Also Ruff (Python) and rustfmt. Use when setting up formatting, replacing Prettier, or wiring CI format checks.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Biome formatter for JS/TS/JSON/CSS — the modern Prettier/ESLint replacement. Also Ruff (Python) and rustfmt. Use when setting up formatting, replacing Prettier, or wiring CI format checks.
Parse STATUS= and the ISSUES: block from the output. The KEY=VALUE lines
report formatter detection (BIOME, PRETTIER, RUFF_FORMAT, BLACK,
RUSTFMT, EDITORCONFIG), integration signals (FORMAT_SCRIPT,
PRE_COMMIT_FORMAT, CI_FORMAT), and a RECOMMENDATION of configured
(a modern formatter is set up), migrate (a legacy formatter wants migration to
Biome/Ruff), or setup (no formatter detected).
Modern formatting preferences:
JavaScript/TypeScript: Biome (replaces Prettier + ESLint). On RECOMMENDATION=migrate with Prettier present, offer migration to Biome — do not configure Prettier as the target formatter.
Python: Ruff format (replaces Black)
Rust: rustfmt (standard)
Step 2: Generate compliance report
Print a formatted compliance report:
Code Formatting Compliance Report
==================================
Project: [name]
Language: [detected]
Formatter: [detected]
Configuration: [status per check]
Format Options: [status per check]
Scripts: [status per check]
Integration: [status per check]
Overall: [X issues found]
Recommendations: [list specific fixes]
If --check-only, stop here.
Step 3: Install and configure formatter (if --fix or user confirms)
Based on detected language and formatter preference, install and configure. Use configuration templates from REFERENCE.md.