Question 1

pre-commit vs husky, which is better for my project?

Accepted Answer

pre-commit is language-agnostic and ideal for multi-language projects, while husky is Node.js-specific. If you work with multiple languages, pre-commit offers more flexibility; for pure JavaScript/TypeScript, husky might integrate more seamlessly with npm.

Question 2

how to add a custom Python script as a pre-commit hook?

Accepted Answer

Define it in your .pre-commit-config.yaml with repo: local and specify the entry point. For example, add a hook with id: custom-check and entry: python scripts/check.py, ensuring the script is executable and returns a non-zero code on failure.

Question 3

why are my pre-commit hooks not running after installation?

Accepted Answer

Verify that pre-commit is installed globally or in a virtual environment, and run pre-commit install to set up Git hooks. Also, check that .pre-commit-config.yaml is in the project root and contains valid hook definitions.

Question 4

can I skip a failing hook temporarily in pre-commit?

Accepted Answer

Yes, use the SKIP environment variable (e.g., SKIP=flake8 git commit) to bypass specific hooks, or git commit --no-verify to skip all hooks. However, overuse can undermine code quality enforcement.

Question 5

how to speed up slow pre-commit hook runs?

Accepted Answer

Enable caching by setting cache: true in the config, and reduce the number of hooks or use lighter alternatives. Also, pre-install dependencies or use hooks with minimal setup to avoid download delays on each run.

Question 6

what are some essential pre-commit hooks for a JavaScript project?

Accepted Answer

Common hooks include prettier for code formatting, eslint for linting, and husky-pre-commit for Node.js integration. These can be sourced from the pre-commit hook repository or custom-configured for specific needs.

pre-commit

What is pre-commit?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions