Lint Rule Development
CheckedThis skill helps you define custom lint rules to enforce coding standards and best practices, improving code quality and consistency.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add biomejs/biome --skill lint-rule-development -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
biomejs
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned biomejs/biome at ef0edd4a2f.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- ef0edd4a2f
- Scanned
- 1 file, 139 lines
About this skill
What it does
This skill assists in developing custom lint rules for Biome, a JavaScript and related language tooling platform. It provides scaffolding to generate initial rule structures, implementation patterns, testing workflows, and documentation guidelines. The skill streamlines the process of creating new linting rules to enforce coding standards and best practices within your codebase.
When to use it
- You need to create a custom lint rule for JavaScript, CSS, JSON, or GraphQL code.
- You are contributing to the Biome project by adding new linting capabilities.
- You want to enforce specific coding standards that aren't covered by existing Biome rules.
- You require assistance with implementing rules that utilize Biome’s semantic model for more advanced analysis.
Key capabilities
- Generates scaffolding for JavaScript, CSS, JSON, and GraphQL lint rules using
just new-js-lintrule,just new-css-lintrule,just new-json-lintrule, orjust new-graphql-lintrule. - Provides a basic rule structure template.
- Includes guidance on implementing linting logic and diagnostics.
- Demonstrates how to use Biome's semantic model for binding analysis within rules.
- Offers instructions for adding code actions (fixes) to automatically correct violations of the new lint rule.
Example prompts
- "Create a JavaScript lint rule named 'useMyRuleName'."
- "Generate scaffolding for a CSS lint rule called 'myRuleName'."
- "Show me an example of how to use the semantic model in a Biome lint rule."
Tips & gotchas
- You must first install required tools using
just install-tools. Ensure cargo, just, and pnpm are available. - Refer to
crates/biome_analyze/CONTRIBUTING.mdfor detailed concepts and contribution guidelines related to Biome lint rules. - The generated rule is initially placed in
crates/biome_js_analyze/src/lint/nursery/use_my_rule_name.rs.