Runs Biome linting and formatting, treating results as blocking requirements.

Install

mkdir -p .claude/skills/biome && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9567" && unzip -o skill.zip -d .claude/skills/biome && rm skill.zip

Installs to .claude/skills/biome

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Enforce Biome formatting and lint discipline in this repository. Use when making any file edits, when asked to run format/lint, and immediately before any commit. Always execute `bun run lint` (from package.json), apply resulting fixes, and re-run until clean. Treat `bun run lint:links` as optional by default, and recommend it when files under `content/` are changed.
369 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Beginner

Key capabilities

  • Format code
  • Lint code
  • Enforce discipline
  • Run lint checks

How it works

Enforces formatting and linting rules using Biome.

Inputs & outputs

You give it
Code edits
You get back
Formatted/linted code

When to use biome

  • Formatting code after edits
  • Running a lint check before a commit
  • Enforcing consistent coding standards

About this skill

Biome

Required Policy

Apply this policy on every task in this repository:

  1. Run bun run lint after making any file change.
  2. Run bun run lint again immediately before any git commit.
  3. Treat lint failures as blocking. Do not proceed to final delivery or commit until lint passes.

Workflow

  1. Make the requested code or content edits.
  2. Execute:
bun run lint
  1. If lint reports issues or rewrites files, review changed files and run bun run lint again until it exits cleanly.
  2. If a commit is requested, run bun run lint one final time right before git commit.
  3. Record lint execution in the task evidence/summary.

Optional Link Check Policy

  • Default: do not run bun run lint:links.
  • If the change includes files under content/, recommend running bun run lint:links.
  • If the user explicitly asks for full check, run bun run check.

Guardrails

  • Use bun run lint as the source of truth command (defined in package.json as biome check --write).
  • Do not replace this with direct biome CLI variants unless user explicitly asks for a different command.
  • Keep bun run lint:links optional unless content/ changed or the user explicitly requests it.
  • Keep lint-induced edits in scope; avoid unrelated refactors.

When not to use it

  • Replacing with direct CLI variants
  • Ignoring lint failures

Prerequisites

Biome installed

Limitations

  • Lint failures are blocking
  • Keep lint-induced edits in scope

How it compares

Requires clean lint checks before any final delivery or commit.

Compared to similar skills

biome side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
biome (this skill)05moReviewBeginner
nx-workspace46moReviewBeginner
windsurf-linting-config12moReviewIntermediate
code-lint02moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

nx-workspace

nrwl

Explore and understand Nx workspaces. USE WHEN answering any questions about the nx workspace, the projects in it or tasks to run. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What targets can I run?', 'What's affected by my changes?', 'Which projects depend on library Y?', or any questions about Nx workspace structure, project configuration, or available tasks.

411

windsurf-linting-config

jeremylongshore

Configure and enforce code quality with AI-assisted linting. Activate when users mention "configure linting", "eslint setup", "code quality rules", "linting configuration", or "code standards". Handles linting tool configuration. Use when configuring systems or services. Trigger with phrases like "windsurf linting config", "windsurf config", "windsurf".

12

code-lint

tomsoulage-dedalus

Formate avec Prettier, lint avec ESLint (auto-fix) les fichiers modifiés. Si tout est propre, propose un commit des corrections.

00

fix-dependabot-alerts

microsoft

Fix Dependabot security alerts by updating vulnerable npm dependencies. Use when the user mentions "dependabot", "security alerts", "vulnerability", "CVE", or wants to update packages with security issues.

1872

dependency-upgrade

wshobson

Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.

26240

typescript-review

metabase

Review TypeScript and JavaScript code changes for compliance with Metabase coding standards, style violations, and code quality issues. Use when reviewing pull requests or diffs containing TypeScript/JavaScript code.

39178

Search skills

Search the agent skills registry