メニュー
Modern linters: Biome, Ruff, Clippy. Use when setting up linting, migrating ESLint/Prettier to Biome, or wiring lint into pre-commit and CI.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/laurigates/claude-plugins --skill configure-lintingコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
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.
SKILL.md を表示中
SOC 職業分類に基づく
| created | "2025-12-16T00:00:00.000Z" |
| modified | "2026-06-18T00:00:00.000Z" |
| reviewed | "2025-12-16T00:00:00.000Z" |
| description | Modern linters: Biome, Ruff, Clippy. Use when setting up linting, migrating ESLint/Prettier to Biome, or wiring lint into pre-commit and CI. |
| allowed-tools | Glob, Grep, Read, Write, Edit, Bash, AskUserQuestion, TodoWrite, WebSearch, WebFetch |
| args | [--check-only] [--fix] [--linter <biome|ruff|clippy>] |
| argument-hint | [--check-only] [--fix] [--linter <biome|ruff|clippy>] |
| name | configure-linting |
Check and configure linting tools against modern best practices.
| Use this skill when... | Use another approach when... |
|---|---|
| Setting up modern linting (Biome, Ruff, Clippy) | Just running linter (use /lint:check skill) |
| Migrating from ESLint/Prettier to Biome | Linters already properly configured |
| Validating linter configuration | Fixing specific lint errors (run linter and fix) |
| Ensuring language-specific best practices | Simple script with no linting needs |
| Configuring pre-commit lint integration | Debugging linter issues (check linter logs) |
pwdfind . -maxdepth 1 -name 'biome.json' -o -name 'biome.jsonc'find . -maxdepth 1 -name 'pyproject.toml' -exec grep -l 'tool.ruff' {} +find . -maxdepth 1 -name 'Cargo.toml' -exec grep -l 'lints.clippy' {} +find . -maxdepth 1 \( -name '.eslintrc*' -o -name '.flake8' -o -name '.pylintrc' \)find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' \)find . -maxdepth 1 -name '.pre-commit-config.yaml'find . -path '*/.github/workflows/*' -maxdepth 3 -name '*.yml'Parse from $ARGUMENTS:
--check-only: Report linting compliance status without modifications--fix: Apply all fixes automatically without prompting--linter <biome|ruff|clippy>: Override auto-detection and force specific linterModern linting preferences:
Execute this linting configuration check:
Read the context values above and determine:
| Indicator | Language | Detected Linter |
|---|---|---|
biome.json | JavaScript/TypeScript | Biome |
pyproject.toml [tool.ruff] | Python | Ruff |
.flake8 | Python | Flake8 (legacy) |
Cargo.toml [lints.clippy] | Rust | Clippy |
If --linter flag is set, use that linter regardless of detection.
Use WebSearch or WebFetch to check current versions:
For each detected linter, check configuration completeness:
Biome (for JS/TS):
Ruff (for Python):
pyproject.toml has [tool.ruff] sectionClippy:
Cargo.toml has [lints.clippy] sectionPrint a compliance report covering:
End with overall issue count and recommendations.
If --check-only is set, stop here.
Apply configuration using templates from REFERENCE.md.
For Biome (JS/TS):
biome.json with recommended ruleslint, lint:fix, format, check)For Ruff (Python):
uv add --group dev ruff[tool.ruff] section to pyproject.tomlFor Clippy (Rust):
[lints.clippy] section to Cargo.tomlIf legacy linters are detected (ESLint, Flake8, etc.), offer migration. See migration guides in REFERENCE.md.
.pre-commit-config.yamlUpdate .project-standards.yaml:
components:
linting: "2025.1"
linting_tool: "[biome|ruff|clippy]"
linting_pre_commit: true
linting_ci: true
Print a summary of all changes applied, scripts added, integrations configured, and next steps for the user.
For detailed configuration templates, migration guides, and CI integration patterns, see REFERENCE.md.
| Context | Command |
|---|---|
| Detect linter config | find . -maxdepth 1 \( -name 'biome.json' -o -name 'ruff.toml' -o -name '.eslintrc*' \) 2>/dev/null |
| Check Biome config | test -f biome.json && jq -c '.linter' biome.json 2>/dev/null |
| Check Ruff in pyproject | grep -A5 '\[tool.ruff\]' pyproject.toml 2>/dev/null |
| List lint scripts | jq -r '.scripts | to_entries[] | select(.key | contains("lint")) | "\\(.key): \\(.value)"' package.json 2>/dev/null |
| Quick compliance check | /configure:linting --check-only |
| Auto-fix configuration | /configure:linting --fix |
| Flag | Description |
|---|---|
--check-only | Report status without offering fixes |
--fix | Apply all fixes automatically without prompting |
--linter <linter> | Override linter detection (biome, ruff, clippy) |
# Check compliance and offer fixes
/configure:linting
# Check only, no modifications
/configure:linting --check-only
# Auto-fix and migrate to Biome
/configure:linting --fix --linter biome
/configure:formatting - Configure code formatting/configure:pre-commit - Pre-commit hook configuration/configure:all - Run all compliance checks