Skip to main content
configure-linting Modern linters: Biome, Ruff, Clippy. Use when setting up linting, migrating ESLint/Prettier to Biome, or wiring lint into pre-commit and CI.
Aller à l'installation Skills Marketplace Découvrez et explorez les compétences IA créées par la communauté.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Copier le promptAfficher les détails du prompt Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/laurigates/claude-plugins --skill configure-lintingLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Télécharger Zip Téléchargement... Plus depuis ce dépôt 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.
Explorateur de fichiers
2 fichiers Métiers associés SOC
Basé sur la classification professionnelle 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
/configure:linting
Check and configure linting tools against modern best practices.
When to Use This Skill
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)
Context
Project root: !pwd
Biome config: !find . -maxdepth 1 -name 'biome.json' -o -name 'biome.jsonc'
Ruff config: !find . -maxdepth 1 -name 'pyproject.toml' -exec grep -l 'tool.ruff' {} +
Clippy config: !find . -maxdepth 1 -name 'Cargo.toml' -exec grep -l 'lints.clippy' {} +
Legacy linters: !find . -maxdepth 1 \( -name '.eslintrc*' -o -name '.flake8' -o -name '.pylintrc' \)
Package files: !find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' \)
Pre-commit config: !find . -maxdepth 1 -name '.pre-commit-config.yaml'
CI workflows: !find . -path '*/.github/workflows/*' -maxdepth 3 -name '*.yml'
Parameters
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 linter
Modern linting preferences:
JavaScript/TypeScript : Biome (unified linter + formatter, fast)
Python : Ruff (replaces flake8, isort, pyupgrade)
Rust : Clippy with workspace lints
Execution
Execute this linting configuration check:
Step 1: Detect project language and existing linters
Read the context values above and determine:
Indicator Language Detected Linter biome.jsonJavaScript/TypeScript Biome pyproject.toml [tool.ruff]Python Ruff .flake8Python Flake8 (legacy) Cargo.toml [lints.clippy]Rust Clippy
If --linter flag is set, use that linter regardless of detection.
Step 2: Verify latest tool versions Use WebSearch or WebFetch to check current versions:
Step 3: Analyze current linter configuration For each detected linter, check configuration completeness:
Config file exists with linter rules
Formatter configured
File patterns and ignores set
Recommended rules enabled
pyproject.toml has [tool.ruff] section
Rules selected (E, F, I, N, etc.)
Line length and target Python version set
Cargo.toml has [lints.clippy] section
Pedantic lints enabled
Workspace-level lints if applicable
Step 4: Generate compliance report Print a compliance report covering:
Config file status (exists / missing)
Linter enabled status
Rules configuration (recommended / minimal / missing)
Formatter integration
Ignore patterns
Lint scripts in package.json / Makefile
Pre-commit hook integration
CI/CD check integration
End with overall issue count and recommendations.
If --check-only is set, stop here.
Step 5: Configure linting (if --fix or user confirms)
Install Biome as dev dependency
Create biome.json with recommended rules
Add npm scripts (lint, lint:fix, format, check)
Install Ruff via uv add --group dev ruff
Add [tool.ruff] section to pyproject.toml
Configure rules, line length, target version
Add [lints.clippy] section to Cargo.toml
Enable pedantic lints
Configure workspace-level lints if applicable
If legacy linters are detected (ESLint, Flake8, etc.), offer migration. See migration guides in REFERENCE.md .
Step 6: Configure pre-commit and CI integration
Add linter pre-commit hook to .pre-commit-config.yaml
Add linter CI check to GitHub Actions workflow
Use templates from REFERENCE.md
Step 7: Update standards tracking Update .project-standards.yaml:
components:
linting: "2025.1"
linting_tool: "[biome|ruff|clippy]"
linting_pre_commit: true
linting_ci: true
Step 8: Print final compliance report 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 .
Agentic Optimizations Context Command Detect linter config find . -maxdepth 1 \( -name 'biome.json' -o -name 'ruff.toml' -o -name '.eslintrc*' \) 2>/dev/nullCheck Biome config test -f biome.json && jq -c '.linter' biome.json 2>/dev/nullCheck Ruff in pyproject grep -A5 '\[tool.ruff\]' pyproject.toml 2>/dev/nullList lint scripts jq -r '.scripts | to_entries[] | select(.key | contains("lint")) | "\\(.key): \\(.value)"' package.json 2>/dev/nullQuick compliance check /configure:linting --check-onlyAuto-fix configuration /configure:linting --fix
Flags Flag Description --check-onlyReport status without offering fixes --fixApply all fixes automatically without prompting --linter <linter>Override linter detection (biome, ruff, clippy)
Examples
/configure:linting
/configure:linting --check-only
/configure:linting --fix --linter biome
Error Handling
Multiple linters detected : Warn about conflict, suggest migration
No package manager found : Cannot install linter, error
Invalid configuration : Report parse error, offer to replace with template
Missing dependencies : Offer to install required packages
See Also