biomejs/pre-commit

Biome's pre-commit hooks.

81

stars

194

commits

Sep 4, 2026

updated

README

pre-commit hooks

This repository provides Biome hooks for pre-commit.

The following section assumes that you installed pre-commit and run pre-commit install in your repository.

Using biome's pre-commit hooks

Biome provides four hooks:

hook iddescription
biome-ciCheck formatting, check if imports are organized, and lints
biome-checkFormat, organize imports, lint, and apply safe fixes to the committed files
biome-formatFormat the committed files
biome-lintLint and apply safe fixes to the committed files

For example, if you want to use the biome-check hook, add the following pre-commit configuration to the root of your project in a file named .pre-commit-config.yaml:

repos:
  - repo: https://github.com/biomejs/pre-commit
    rev: v2.5.10 # Use the sha / tag you want to point at
    hooks:
      - id: biome-check

Using biome with a local pre-commit hook

If Biome is already installed as a npm package in your local repository, then it can be a burden to update both package.json and .pre-commit-config.yaml when you update Biome. Instead of using the provided Biome hooks, you can specify your own local hook.

For example, if you use npm, you can write the following hook in .pre-commit-config.yaml:

repos:
  - repo: local
    hooks:
      - id: local-biome-check
        name: biome check
        entry: npx biome check --write --files-ignore-unknown=true --no-errors-on-unmatched
        language: system
        types: [text]
        files: "\\.(jsx?|tsx?|c(js|ts)|m(js|ts)|d\\.(ts|cts|mts)|jsonc?|css|svelte|vue|astro|graphql|gql)$"

The pre-commit option files is optional, because Biome is able to ignore unknown files (using the option --files-ignore-unknown=true).

Contributors

ematipico

138 commits

renovate[bot]

11 commits

yxtay

3 commits

biomejs/pre-commit

Biome's pre-commit hooks.

81

stars

194

commits

Sep 4, 2026

updated

README

pre-commit hooks

This repository provides Biome hooks for pre-commit.

The following section assumes that you installed pre-commit and run pre-commit install in your repository.

Using biome's pre-commit hooks

Biome provides four hooks:

hook iddescription
biome-ciCheck formatting, check if imports are organized, and lints
biome-checkFormat, organize imports, lint, and apply safe fixes to the committed files
biome-formatFormat the committed files
biome-lintLint and apply safe fixes to the committed files

For example, if you want to use the biome-check hook, add the following pre-commit configuration to the root of your project in a file named .pre-commit-config.yaml:

repos:
  - repo: https://github.com/biomejs/pre-commit
    rev: v2.5.10 # Use the sha / tag you want to point at
    hooks:
      - id: biome-check

Using biome with a local pre-commit hook

If Biome is already installed as a npm package in your local repository, then it can be a burden to update both package.json and .pre-commit-config.yaml when you update Biome. Instead of using the provided Biome hooks, you can specify your own local hook.

For example, if you use npm, you can write the following hook in .pre-commit-config.yaml:

repos:
  - repo: local
    hooks:
      - id: local-biome-check
        name: biome check
        entry: npx biome check --write --files-ignore-unknown=true --no-errors-on-unmatched
        language: system
        types: [text]
        files: "\\.(jsx?|tsx?|c(js|ts)|m(js|ts)|d\\.(ts|cts|mts)|jsonc?|css|svelte|vue|astro|graphql|gql)$"

The pre-commit option files is optional, because Biome is able to ignore unknown files (using the option --files-ignore-unknown=true).

Contributors

ematipico

138 commits

renovate[bot]

11 commits

yxtay

3 commits