biomejs

Name: biomejs
Availability: InStock
Author: pantheon-org

Resolve BiomeJS linting errors and warnings with fix-forward corrections.

1|Updated Dec 5, 2025

Search Tags:#automation #linting #biome #code-quality #static-analysis #ci #fix-forward

Ready to run

npx skills add https://github.com/pantheon-org/opencode-plugins --skill biomejs-pantheon-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: biomejs
Source: https://github.com/pantheon-org/opencode-plugins/tree/main/.opencode/skills/biomejs
Command: npx skills add https://github.com/pantheon-org/opencode-plugins --skill biomejs-pantheon-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BiomeJS linting can block progress with warnings and errors that tempt suppression. This Skill resolves BiomeJS linting issues with a fix-forward approach that addresses root causes rather than silencing them.

Core Features & Use Cases

Never suppress rules: Prohibits biome-ignore comments and suppression directives to maintain code quality.
Fix-forward workflow: Encourages automated and manual fixes that address root causes rather than masking symptoms.
CI & local development ready: Integrates with biome check, biome check --write, and biome format to streamline refactors and reviews.
Broad rule coverage: Addresses formatting, correctness, suspicious patterns, style, complexity, and performance rules for consistent quality.

Quick Start

Check for issues: biome check .
Apply safe fixes: biome check --write .
Review remaining issues: biome check --verbose .

Frequently Asked Questions about biomejs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix BiomeJS linting errors without suppressing rules?▼

Fix BiomeJS linting errors without suppressing rules by applying a fix-forward approach that addresses root causes. This workflow resolves formatting, correctness, and style issues using `biome check --write` while strictly prohibiting `biome-ignore` comments.

Can I use BiomeJS to automatically format and lint code in CI pipelines?▼

Yes, BiomeJS integrates with CI pipelines to automate formatting and linting. Run `biome check` to identify issues across correctness and performance rules, then apply safe automated fixes to streamline code reviews without introducing suppressions.

What is a fix-forward approach for static analysis warnings?▼

A fix-forward approach for static analysis warnings resolves the root cause of code quality issues rather than masking symptoms. It encourages using automated tooling to fix suspicious patterns and complexity rules instead of adding suppression directives.

Does BiomeJS cover performance and complexity rules for code quality?▼

BiomeJS covers performance and complexity rules alongside formatting, correctness, suspicious patterns, and style. This broad rule coverage ensures consistent code quality by identifying and verifying these issues during local development and CI.

Why should I avoid biome-ignore comments when resolving lint issues?▼

Avoid `biome-ignore` comments because they silence warnings by masking symptoms rather than addressing root causes. Prohibiting suppression directives maintains actual code quality by enforcing a fix-forward workflow that resolves formatting and correctness issues.

What's the best way to apply safe fixes for BiomeJS lint issues?▼

The best way to apply safe fixes for BiomeJS lint issues is running `biome check --write`. This command automatically addresses formatting, style, and correctness rules, allowing you to review any remaining issues with `biome check --verbose`.