G2

Aditya S.

Software Developer

Enterprise (> 1000 emp.)

7/17/2026

"Effortless Team-Wide Git Hook Enforcement That Just Works"

4.5/5

What do you like best about Husky?

Husky makes it effortless to enforce git hooks (pre-commit, pre-push, commit-msg) across a team without everyone having to remember to run linting or tests manually. Setup is quick, it integrates cleanly with npm/yarn scripts, and it catches issues — bad formatting, failing tests, broken commit conventions — before they ever hit the shared repo. It's lightweight, well-maintained, and just works without much configuration overhead. Review collected by and hosted on G2.com.

What do you dislike about Husky?

A few common frustrations: the config migrated from a .huskyrc file to shell scripts in a .husky/ directory a while back, and that transition broke a lot of existing setups and required manual migration. Hooks can also silently fail to run if a teammate doesn't have prepare scripts set up right after cloning, which leads to inconsistent enforcement across the team. It also adds a bit of overhead to every commit/push, which can feel slow on large repos, and debugging why a hook isn't firing (permissions, shell differences across OS) can be more fiddly than it should be. Review collected by and hosted on G2.com.

What problems is Husky solving and how is that benefiting you?

Husky solves the problem of relying on developers to remember to lint, format, or test their code before committing or pushing. By enforcing these checks automatically at the git hook level, it stops broken or non-compliant code from entering the repo in the first place, rather than catching it later in CI or code review. This has benefited us by cutting down on "fix lint" or "fix tests" follow-up commits, keeping commit history and messages more consistent, and reducing the number of avoidable failures that show up in CI — which saves both build time and reviewer time. Review collected by and hosted on G2.com.