Skip to main content
configure-formatting 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.
설치로 이동 Skills Marketplace 커뮤니티가 만든 AI 스킬을 발견하고 탐색하세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/laurigates/claude-plugins --skill configure-formatting명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Zip 다운로드 다운로드 중... 이 저장소의 다른 Skills Install, 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.
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
/configure:formatting
Check and configure code formatting tools against modern best practices.
When to Use This Skill
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
Context
Biome config: !find . -maxdepth 1 -name \'biome.json\'
Prettier config: !find . -maxdepth 1 \( -name '.prettierrc*' -o -name 'prettier.config.*' \)
Ruff config: !find . -maxdepth 1 -name 'pyproject.toml' -exec grep -l 'tool.ruff.format' {} +
Black config: !find . -maxdepth 1 -name 'pyproject.toml' -exec grep -l 'tool.black' {} +
Rustfmt config: !find . -maxdepth 1 \( -name 'rustfmt.toml' -o -name '.rustfmt.toml' \)
EditorConfig: !find . -maxdepth 1 -name \'.editorconfig\'
Package JSON: !find . -maxdepth 1 -name \'package.json\'
Python project: !find . -maxdepth 1 -name \'pyproject.toml\'
Rust project: !find . -maxdepth 1 -name \'Cargo.toml\'
Pre-commit: !find . -maxdepth 1 -name \'.pre-commit-config.yaml\'
Project standards: !find . -maxdepth 1 -name \'.project-standards.yaml\'
Parameters
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)
Version Checking CRITICAL : Before flagging outdated formatters, verify latest releases using WebSearch or WebFetch:
Execution Execute this code formatting configuration workflow:
Step 1: Detect formatters and integration state 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:
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 .
Install formatter package
Create configuration file (biome.json, pyproject.toml section, rustfmt.toml)
Add format scripts to package.json or Makefile/justfile
Configure ignore patterns in the formatter config (e.g. files.includes in biome.json)
Step 4: Create EditorConfig integration Create or update .editorconfig with settings matching the formatter configuration.
Step 5: Handle migrations (if applicable) If legacy formatter detected (Prettier -> Biome, Black -> Ruff):
Import existing configuration
Install new formatter
Remove old formatter
Update scripts
Update pre-commit hooks
Step 6: Configure pre-commit hooks Add formatter to .pre-commit-config.yaml using the appropriate hook repository.
Step 7: Configure CI/CD integration Add format check step to GitHub Actions workflow.
Step 8: Configure editor integration Create or update .vscode/settings.json with format-on-save and .vscode/extensions.json with formatter extension.
Step 9: Update standards tracking Update .project-standards.yaml:
components:
formatting: "2025.1"
formatting_tool: "[biome|ruff|rustfmt]"
formatting_pre_commit: true
formatting_ci: true
Step 10: Print completion report 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 .
Agentic Optimizations Context Command Quick compliance check /configure:formatting --check-onlyAuto-fix all issues /configure:formatting --fixCheck Biome formatting biome format --check --reporter=githubCheck Ruff formatting ruff format --check --output-format=githubCheck rustfmt formatting `cargo fmt --check 2>&1
Flags Flag Description --check-onlyReport status without offering fixes --fixApply all fixes automatically without prompting --formatter <formatter>Override formatter detection (biome, ruff, rustfmt)
Examples
/configure:formatting
/configure:formatting --check-only
/configure:formatting --fix --formatter biome
Error Handling
Multiple formatters detected : Warn about conflict, suggest migration
No package manager found : Cannot install formatter, error
Invalid configuration : Report parse error, offer to replace with template
Formatting conflicts : Report files that would be reformatted
See Also