Git Hooks with Husky and lint-staged: The Complete Setup Guide for 2025

Every time you've caught a forgotten console.log , a TypeScript error, or an unformatted file in a code review — that's time you could have saved with Git hooks. They run automatically before commits, catching problems before they reach the repository. Husky makes Git hooks easy to set up. lint-staged makes them fast by only running on changed files. What Are Git Hooks? Git hooks are shell scripts that run at specific points in the Git workflow: pre-commit : Runs before a commit is created commit-msg : Validates the commit message format pre-push : Runs before a push post-merge : Runs after a merge The most useful for daily development is pre-commit — it's the last line of defense before code enters the repo. Why Husky? Git hooks live in .git/hooks/ which isn't tracked by version control. This means: New team members don't get hooks automatically CI doesn't enforce the same checks as local development Hooks get lost when you re-clone the repo Husky solves this by storing hooks in a tra