4.4 KiB
Difference from pre-commit
General differences
preksupports both.pre-commit-config.yamland.pre-commit-config.ymlconfiguration files.prekimplements some common hooks frompre-commit-hooksin Rust for better performance.prekuses~/.cache/prekas the default cache directory for repos, environments and toolchains.prekdecoupled hook environment from their repositories, allowing shared toolchains and environments across hooks.preksupportslanguage_versionas a semver specifier and automatically installs the required toolchains.
Workspace mode
prek supports workspace mode, allowing you to run hooks for multiple projects in a single command. Each subproject can have its own .pre-commit-config.yaml file.
See Workspace Mode for more information.
Language support
Python
Dependency Management with uv
prek uses uv for creating virtual environments and installing dependencies:
- First tries to find
uvin the system PATH - If not found, automatically installs
uvfrom the best available source (GitHub releases, PyPI, or mirrors) - Automatically installs the required Python version if it's not already available
PEP 723 Inline Script Metadata Support
For Python hooks without additional_dependencies, prek can read PEP 723 inline metadata from the script specified in the entry field.
Example:
.pre-commit-config.yaml:
repos:
- repo: local
hooks:
- id: echo
name: echo
language: python
entry: ./echo.py
echo.py:
# /// script
# requires-python = ">=3.13"
# dependencies = [
# "pyecho-cli",
# ]
# ///
from pyecho import main
main()
Important Notes:
- The first part of the
entryfield must be a path to a local Python script - If
additional_dependenciesis specified in.pre-commit-config.yaml, script metadata will be ignored - When both
language_version(in config) andrequires-python(in script) are set,language_versiontakes precedence - Only
dependenciesandrequires-pythonfields are supported; other metadata liketool.uvis ignored
Ruby
prek does not currently support installing a new version of Ruby to run Ruby hooks. All versions of Ruby found in the system PATH will be considered based on their version, and common locations used by Ruby version managers (such as rvm, rbenv, mise, asdf, and homebrew) will be also be checked. language_version can be used to specify the required Ruby version, and the hook will fail if a suitable Ruby version is not found.
Gems specified in hook gemspec files and additional_dependencies will be installed into an isolated gemset for Ruby hooks. This gemset will be shared between hooks that use the same Ruby version and have the same set of dependencies, including across different repositories.
Docker & Docker Image
prek auto-detects the available container runtime on the system (Docker or Podman) and uses it to run container-based hooks. You can also explicitly specify the container runtime using the PREK_CONTAINER_RUNTIME environment variable.
Command line interface
prek run
prek run [HOOK|PROJECT]...supports selecting or skipping multiple projects or hooks in workspace mode. See Running Specific Hooks or Projects for details.prekprovides dynamic completions of hook id.prek run --last-committo run hooks on files changed by the last commit.prek run --directory <DIR>to run hooks on a specified directory.
prek list
prek list command lists all available hooks, their ids, and descriptions. This provides a better overview of the configured hooks.
prek auto-update
prek auto-updateupdates all projects in the workspace to their latest revisions.prek auto-updatechecks updates for the same repository only once, speeding up the process in workspace mode.prek auto-updatesupports--dry-runoption to preview the updates without applying them.
prek sample-config
prek sample-configcommand has a--fileoption to write the sample configuration to a specific file.
prek cache
prek cache cleanto remove all cached data.prek cache gcto remove unused cached repositories, environments and toolchains.prek cache dirto show the cache directory.
prek clean and prek gc are also available but hidden, as prek cache is preferred.