aiko-atami/biomejs
skills/biomejs/SKILL.md
Configure and operate BiomeJS in JavaScript/TypeScript projects, including installation, `biome.json` setup, formatter/linter/check workflows, VCS integration, and CI usage. Use when users ask to adopt Biome, tune rules/includes, set up monorepo/shared configs, or troubleshoot Biome command behavior.
development
Updated Mar 27, 2026
$ install --global
skillsauthnpx skillsauth add aiko-atami/biomejs-skill biomejsInstall 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: Mar 30, 2026, 4:44 PM55.6s10 files scanned
SKILL.md
- name:
- biomejs
- description:
- Configure and operate BiomeJS in JavaScript/TypeScript projects, including installation, `biome.json` setup, formatter/linter/check workflows, VCS integration, and CI usage. Use when users ask to adopt Biome, tune rules/includes, set up monorepo/shared configs, or troubleshoot Biome command behavior.
BiomeJS
Use this skill to implement and operate BiomeJS with predictable steps and minimal disruption.
For ESLint/Prettier migration, use the dedicated eslint-prettier-migration skill.
Workflow
- Identify intent:
- Fresh setup
- Config tuning
- CI/VCS integration
- Diagnostics troubleshooting
- Apply the matching path:
- Fresh setup: follow
references/getting-started.md - Config and file-scoping: follow
references/configuration-and-vcs.md - Advanced config templates: follow
references/advanced-configuration-templates.md - CLI options/reporters: follow
references/cli-basics.md - Monorepo and shared config strategy: follow
references/monorepo-and-upgrades.md - Performance debugging: follow
references/performance-tracing.md - Pre-commit hooks and CI recipes: follow
references/automation-ci-and-hooks.md
- Verify with a no-write pass before auto-fixing:
- Run
biome check . - Then run
biome check --writeonly after confirming scope and intended changes
Operational Defaults
Use these defaults unless user asks otherwise:
- Pin Biome version when installing (
-Ewith package managers that support it). - Keep config in project root (
biome.jsonorbiome.jsonc). - Run
biome check --writefor unified format+lint+organize imports. - Run
biome ciin CI pipelines.
References
- Setup and baseline commands:
references/getting-started.md - Configuration, includes, and VCS integration:
references/configuration-and-vcs.md - Advanced configuration templates and migration-safe patterns:
references/advanced-configuration-templates.md - Useful CLI commands and options:
references/cli-basics.md - Monorepo setup and v1->v2 upgrade notes:
references/monorepo-and-upgrades.md - Slowness investigation and tracing spans:
references/performance-tracing.md - Git hooks and CI recipes:
references/automation-ci-and-hooks.md
Related Skills
aiko-atami/eslint-prettier-migration
development
VerifiedTrustedCommunity
Migrate projects from ESLint and/or Prettier to BiomeJS with safe sequencing, flag selection (`--include-inspired`, `--include-nursery`), config-translation review, ignore parity checks, and post-migration stabilization. Use when users ask to replace ESLint/Prettier, port legacy or flat ESLint configs, migrate Prettier options/ignores, or troubleshoot migration command limits and behavior differences.
SKILL.mdUpdated Mar 27, 2026
openclaw/openclaw-secret-scanning-maintainer
development
VerifiedTrustedCommunity
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
357,764SKILL.mdUpdated Apr 15, 2026
openclaw/openclaw-release-maintainer
development
VerifiedTrustedCommunity
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/openclaw-qa-testing
development
VerifiedTrustedCommunity
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
357,764SKILL.mdUpdated Apr 10, 2026