shipshitdev/biome-validator
skills/biome-validator/SKILL.md
Validate Biome 2.3+ configuration and detect outdated patterns. Ensures proper schema version, domains, assists, and recommended rules. Use before any linting work or when auditing existing projects.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library biome-validatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 14, 2026, 4:48 AM105.9s4 files scanned
SKILL.md
- name:
- biome-validator
- description:
- Validate Biome 2.3+ configuration and detect outdated patterns. Ensures proper schema version, domains, assists, and recommended rules. Use before any linting work or when auditing existing projects.
- version:
- 1.0.1
- tags:
- biome, linter, formatter, validation, code-quality
Biome Validator
When This Activates
- Setting up linting for a new project
- Before any code quality work
- Auditing existing Biome configurations
- After AI generates biome.json
- CI/CD pipeline validation
Quick Start
python3 scripts/validate.py --root .
python3 scripts/validate.py --root . --strict
What Gets Checked
| Check | Good (2.3+) | Bad (legacy) |
|---|---|---|
| Schema version | "$schema": ".../2.3.12/schema.json" | .../1.9.0/schema.json or older |
| Package version | "@biomejs/biome": "^2.3.0" | "^1.9.0" or 2.0-2.2 |
| Linter config | linter.rules.recommended: true | missing or legacy rules shape |
| Assist actions | assist.actions.source.organizeImports | top-level organizeImports.enabled |
| Domains | linter.domains.react / .next: "on" | no domains configured |
| Suppression comments | // biome-ignore lint/<rule>: reason | // eslint-disable, // @ts-ignore |
Biome 2.0+ also adds type-aware linting (no TypeScript compiler required) and multi-file lint analysis.
See references/full-guide.md (§ What Gets Checked, § Biome 2.3+ Features, § Recommended Configuration) for full GOOD/BAD config examples and a complete recommended biome.json.
Deprecated Patterns
| Deprecated | Replacement (2.3+) |
|------------|-------------------|
| organizeImports.enabled | assist.actions.source.organizeImports |
| Schema < 2.0 | Schema 2.3.11+ |
| @biomejs/biome < 2.3 | @biomejs/biome@latest |
| No domains config | Use linter.domains for frameworks |
See references/full-guide.md (§ Validation Output) for a sample validation report.
Migration from ESLint
- Remove ESLint/Prettier packages, add
@biomejs/biome@latest - Generate config:
bunx biome init - Port existing rules:
bunx biome migrate eslint --write - Update
package.jsonlint/format scripts to callbiome - Delete old
.eslintrc*/.prettierrc*/.eslintignore/.prettierignore
See references/full-guide.md (§ Migration from ESLint) for the exact commands per step, plus VS Code editor settings and a CI/CD workflow snippet.
Integration
linter-formatter-init- Sets up Biome from scratchnextjs-validator- Validates Next.js (enable next domain)bun-validator- Validates Bun workspace
Related Skills
shipshitdev/weekly-review
development
VerifiedTrustedCommunity
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/project-board
testing
VerifiedTrustedCommunity
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/board-sync
testing
VerifiedTrustedCommunity
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/how
development
VerifiedTrustedCommunity
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.
35SKILL.mdUpdated Aug 31, 2026