Biome Config Validator

Validate and lint Biome (biome.json) configuration files for structure, rule conflicts, deprecated options, and best practices. 22 rules across structure, li...

Security Scan

The skill's stated purpose (linting/validating biome.json) matches the included code and runtime instructions: it reads and validates local configuration files and does not request credentials or network access, but part of the script text was truncated in the prompt so you should verify the full file before installing.

Purpose & Capability

Name/description (Biome config validator) align with the included script and SKILL.md: the commands run a Python script that parses JSON and applies lint/structure/formatting/best-practice rules. No extraneous credentials, binaries, or unrelated capabilities are requested.

Instruction Scope

The SKILL.md instructs the agent to run the bundled Python script on a specified biome.json and choose output format/commands. The script logic shown operates on the provided file, checks schema, rule groups, patterns, and local 'extends' paths. It does not instruct reading arbitrary system state or network endpoints. Note: the script checks existence of 'extends' paths and will examine local filesystem paths referenced by the config (expected for a validator).

Install Mechanism

No install spec; this is instruction-only plus a bundled Python script. No downloads, package installs, or external installers are present in the provided metadata.

Credentials

The skill declares no environment variables, no credentials, and no config paths. The script as shown only reads files passed on the command line and local paths referenced by the config; it does not require secrets or external tokens.

Persistence & Privilege

The skill is not always-enabled and does not request any persistent system-wide privileges. It runs only when invoked and does not modify other skills or agent-wide settings based on the provided content.

Assessment

This skill is internally coherent for validating biome.json files: it reads the target file and local paths referenced by 'extends' and reports issues. Before installing or running, review the entire scripts/biome_config_validator.py file (the prompt contained a truncated excerpt) to confirm there are no network calls, subprocess executions, or code that transmits data. Run it first in a sandbox or on non-sensitive repositories. Be aware that the validator will attempt to access local files referenced by the config (e.g., extends paths), so avoid running it on directories containing secrets unless you trust the script. If you want extra assurance, search the full script for imports or functions such as requests/urllib/socket/subprocess/os.system/open with remote URLs, or any code that writes out data to external endpoints, and verify those are absent or intentional.

Validate biome.json configuration files for correctness, conflicts, deprecated options, and best practices.

Commands

# Validate a biome.json file (all rules)
python3 scripts/biome_config_validator.py lint biome.json

# Check for rule conflicts only
python3 scripts/biome_config_validator.py conflicts biome.json

# Check for deprecated options
python3 scripts/biome_config_validator.py deprecated biome.json

# Validate structure only
python3 scripts/biome_config_validator.py validate biome.json

# JSON output
python3 scripts/biome_config_validator.py lint biome.json --format json

# Summary only
python3 scripts/biome_config_validator.py lint biome.json --format summary

Rules (22)

Structure (5)

• Invalid JSON syntax
• Unknown top-level keys
• Invalid schema version ($schema URL)
• Missing recommended sections (linter, formatter)
• Invalid file patterns in includes/excludes

Linting (7)

• Unknown lint rule names
• Rules in wrong category
• Conflicting rules (e.g., useConst vs noConst)
• Disabled recommended rules without justification
• Invalid rule severity values
• Empty rule groups
• Deprecated rule names

Formatting (5)

• Invalid indent style/width combination
• Conflicting formatter settings
• Line width out of reasonable range
• Invalid quote style values
• Tab width mismatch with indent width

Best Practices (5)

• Missing VCS integration settings
• Overly broad ignore patterns
• No organizeImports configuration
• Missing JavaScript/TypeScript specific settings
• Extends pointing to non-existent config

Output Formats

• text (default): Human-readable with colors and severity icons
• json: Machine-readable with file, rule, severity, message
• summary: Counts by severity only

Exit Codes

• 0: No issues (or warnings only)
• 1: Errors found
• 2: Invalid input