Hooks mit dem Team mithilfe von Husky teilen

Git hooks live in .git/hooks, which is not part of the repository. So a pre-commit hook you write only runs on your machine.

To enforce standards across a team, hooks must be shareable and version-controlled.

Git can read hooks from a custom directory you commit to the repo via core.hooksPath. This is the foundation most tools build on.

Husky is a popular tool for JavaScript projects that manages hooks via committed files and wires up core.hooksPath automatically on install.

Run the init command. It creates a .husky/ directory and a sample hook, and sets up the prepare script.

Husky relies on npm's prepare lifecycle so hooks are enabled automatically whenever a teammate runs npm install.

Add commands to .husky/pre-commit. Since the file is committed, every contributor gets the same checks.

Linting the whole project on every commit is slow. lint-staged runs tools only on the files you actually staged.

Map file patterns to commands. Below runs the formatter and linter only on staged JS files.

A commit-msg hook can validate message format. Paired with commitlint, it enforces conventional commits across the team.

Husky is Node-centric. Language-agnostic options include pre-commit (Python), lefthook (Go, very fast), and overcommit (Ruby). All solve the same distribution problem.

Remember: client hooks can be bypassed with --no-verify. They catch honest mistakes, but real enforcement must also live in CI and server-side hooks.

Test your shared-hooks knowledge.

You can now share hooks across a team:

• core.hooksPath points Git at a committed hooks directory
• Husky automates setup via the prepare script
• lint-staged runs checks only on staged files
• commitlint enforces message format
• Hooks complement, never replace, server-side and CI enforcement

This builds directly on your client-side and server-side hook lessons.