菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/laurigates/claude-plugins --skill configure-formatting命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| created | "2025-12-16T00:00:00.000Z" |
| modified | "2026-06-18T00:00:00.000Z" |
| reviewed | "2026-06-10T00:00:00.000Z" |
| description | 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. |
| allowed-tools | Glob, Grep, Read, Write, Edit, Bash, AskUserQuestion, TodoWrite, WebSearch, WebFetch |
| args | [--check-only] [--fix] [--formatter <biome|ruff|rustfmt>] |
| argument-hint | [--check-only] [--fix] [--formatter <biome|ruff|rustfmt>] |
| name | configure-formatting |
Check and configure code formatting tools against modern best practices.
| Use this skill when... | Use another approach when... |
|---|---|
| Setting up Biome, Ruff format, or rustfmt for a project | Running an existing formatter (biome format, ruff format) |
| Migrating from Prettier or ESLint to Biome, or Black to Ruff | Fixing individual formatting issues in specific files |
| Auditing formatter configuration for completeness and best practices | Configuring linting rules (/configure:linting instead) |
| Adding format-on-save and CI format checks | Setting up pre-commit hooks only (/configure:pre-commit instead) |
| Standardizing formatting settings across a monorepo | Editing .editorconfig or .vscode/settings.json manually |
find . -maxdepth 1 -name \'biome.json\'find . -maxdepth 1 \( -name '.prettierrc*' -o -name 'prettier.config.*' \)find . -maxdepth 1 -name 'pyproject.toml' -exec grep -l 'tool.ruff.format' {} +find . -maxdepth 1 -name 'pyproject.toml' -exec grep -l 'tool.black' {} +find . -maxdepth 1 \( -name 'rustfmt.toml' -o -name '.rustfmt.toml' \)find . -maxdepth 1 -name \'.editorconfig\'find . -maxdepth 1 -name \'package.json\'find . -maxdepth 1 -name \'pyproject.toml\'find . -maxdepth 1 -name \'Cargo.toml\'find . -maxdepth 1 -name \'.pre-commit-config.yaml\'find . -maxdepth 1 -name \'.project-standards.yaml\'Parse from $ARGUMENTS:
--check-only: Report compliance status without modifications--fix: Apply all fixes automatically without prompting--formatter <formatter>: Override formatter detection (biome, ruff, rustfmt)CRITICAL: Before flagging outdated formatters, verify latest releases using WebSearch or WebFetch:
Execute this code formatting configuration workflow:
Run the detection script to scan the project for formatter config files, script/hook/CI presence, and a recommendation over the detected booleans:
bash "${CLAUDE_SKILL_DIR}/scripts/configure-formatting.sh" --home-dir "$HOME" --project-dir "$(pwd)"
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:
RECOMMENDATION=migrate with Prettier present, offer migration to Biome — do not configure Prettier as the target formatter.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.
Based on detected language and formatter preference, install and configure. Use configuration templates from REFERENCE.md.
files.includes in biome.json)Create or update .editorconfig with settings matching the formatter configuration.
If legacy formatter detected (Prettier -> Biome, Black -> Ruff):
Use migration guides from REFERENCE.md.
Add formatter to .pre-commit-config.yaml using the appropriate hook repository.
Add format check step to GitHub Actions workflow.
Create or update .vscode/settings.json with format-on-save and .vscode/extensions.json with formatter extension.
Update .project-standards.yaml:
components:
formatting: "2025.1"
formatting_tool: "[biome|ruff|rustfmt]"
formatting_pre_commit: true
formatting_ci: true
Print a summary of changes made, scripts added, and next steps (run format, verify CI, enable format-on-save).
For detailed configuration templates, migration guides, and pre-commit configurations, see REFERENCE.md.
| Context | Command |
|---|---|
| Quick compliance check | /configure:formatting --check-only |
| Auto-fix all issues | /configure:formatting --fix |
| Check Biome formatting | biome format --check --reporter=github |
| Check Ruff formatting | ruff format --check --output-format=github |
| Check rustfmt formatting | `cargo fmt --check 2>&1 |
| Flag | Description |
|---|---|
--check-only | Report status without offering fixes |
--fix | Apply all fixes automatically without prompting |
--formatter <formatter> | Override formatter detection (biome, ruff, rustfmt) |
# Check compliance and offer fixes
/configure:formatting
# Check only, no modifications
/configure:formatting --check-only
# Auto-fix and migrate to Biome
/configure:formatting --fix --formatter biome
/configure:linting - Configure linting tools/configure:editor - Configure editor settings/configure:pre-commit - Pre-commit hook configuration/configure:all - Run all compliance checksInstall, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.
FinOps snapshot — org billing, workflow stats, cache usage. Use when you want a high-level view of CI spending or workflow health before diving deeper.
GitHub Actions billing, workflow efficiency, and waste analysis at org or repo level. Use when investigating CI/CD costs, wasted runs, or optimizing triggers.