Awesome pre-commit

A curated list of awesome pre-commit hooks and related resources.

The official list of supported hooks was previously a great resource for discovering new hooks. The new suggested approach of finding hooks works ok, but it can still be difficult to find what you're looking for, or discover new hooks you didn't know you needed. This repo seeks primarily to serve as that resource.

• Hooks
  • C/C++
  • CMake
  • Dockerfile
  • Documentation
  • Images
  • JSON
  • Makefile
  • Markdown
  • Protocol Buffers
  • Python
  • Shell
  • Spellchecking
  • YAML
• Additional Resources and Tips
  • Installing with uv
  • Replacements
  • Tool Setup
    • additional_dependencies
    • Dev Environments

Hooks

C/C++

• https://github.com/pre-commit/mirrors-clang-format - Formats C, C++, Objective-C, and Java code
• https://github.com/Takishima/cmake-pre-commit-hooks - Static analysis hooks leveraging compile_commands.json for CMake-based projects
  • clang-tidy - Linter
  • cppcheck - Static analyzer
  • include-what-you-use - #include linter

CMake

• https://github.com/cheshirekow/cmake-format-precommit
  • cmake-format - Formatter
  • cmake-lint - Linter
• https://github.com/BlankSpruce/gersemi - Formatter
• https://github.com/cmake-lint/cmake-lint - Linter

Dockerfile

• https://github.com/AleksaC/hadolint-py - Linter

Documentation

• https://github.com/adamchainz/blacken-docs - Formats Python code blocks within documentation
• https://github.com/amperser/proselint - Linter

Images

• https://github.com/shssoichiro/oxipng - PNG optimizer

JSON

• https://github.com/maresb/check-json5 - Checks JSON syntax (allows comments, trailing commas, etc.)
• https://github.com/python-jsonschema/check-jsonschema - JSON schema validation

Makefile

• https://github.com/mrtazz/checkmake - Linter

Markdown

• https://github.com/hukkin/mdformat - Formatter
• https://github.com/tcort/markdown-link-check - Checks for dead hyperlinks

Protocol Buffers

• https://github.com/bufbuild/buf
  • buf-generate - Auto-generates source code from proto file
  • buf-breaking - Enforces compatibility when proto file changes
  • buf-lint - Linter
  • buf-format - Formatter
  • buf-dep-update - Updates dependencies
  • buf-dep-prune - Removes unused dependencies
• https://github.com/yoheimuta/protolint - Linter

Python

• https://github.com/charliermarsh/ruff-pre-commit
  • ruff - Linter
  • ruff-format - Formatter
• https://github.com/psf/black
  • black - Formatter
  • black-jupyter - Formatter (for Jupyter Notebooks)

Shell

• https://github.com/MaxWinterstein/shfmt-py - Formatter
• https://github.com/shellcheck-py/shellcheck-py - Linter
• https://github.com/openstack/bashate - Linter/style checker
• https://github.com/lovesegfault/beautysh - Formatter

Spellchecking

• https://github.com/crate-ci/typos - Spell checker/fixer

YAML

• https://github.com/mschuett/yaml-shellcheck
  • yaml-shellcheck - Lints shell scripts in yaml files (such as .gitlab-ci.yml)
• https://github.com/google/yamlfmt - Formatter
• https://github.com/adrienverge/yamllint - Linter

Additional Resources and Tips

Installing with uv

Use uv to speed up installation of python-based hooks:

uv tool install pre-commit --with pre-commit-uv

For more information, refer to https://adamj.eu/tech/2025/05/07/pre-commit-install-uv/

Replacements

• prek
  • Faster
  • Uses less disk space
  • Other enhancements

Tool Setup

When using pre-commit on a development team, it is important for all developers to be using the same versions of the tools that their pre-commit hooks depend on. For many hooks, pre-commit will automatically bootstrap the appropriate package manager (if needed) and install the tools into a Python virtual environment for you; unfortunately other hooks rely on system-installed tools that pre-commit must assume are available. To work around this, there are several options:

additional_dependencies

When you need to use a hook whose language supports the additional_dependencies property, check if the language's package manager has an implementation of the tool, and specify it there. This is somewhat common for Python.

As an example, the hooks for the https://github.com/pocc/pre-commit-hooks repo will not install the tools automatically. But many of the tools can be installed automatically by pre-commit via pip, just by adding the appropriate values to additional_dependencies, such as clang-format or clang-tidy -- just remember to pin the package version!

Dev Environments

Set up a dev environment containing your desired pre-commit hook dependencies (as well as other dependencies) using one of the available options:

• Dev Containers
  • Docker-based
  • Integrates into popular code editors
• Nix Package Manager
• Devbox
  • Nix-based (but more user-friendly)
  • Can be hosted in the Cloud
  • Can generate Dev Container definitions and Dockerfiles
• Pixi
  • Conda-based

When using a non-Docker-based dev environment, it is highly recommended to use direnv (or similar) to automatically activate your dev environment when you enter your project's directory.