Husky is a tool that allows pushy bastards to inject trojans into other developers’ machines. This is really cool if you work with a bunch of morons you can’t trust to operate their own tools. I see why dictators love it.
I have this crazy idea, though, that how code is produced is not my concern. You can use freaking Notepad.exe for all I care. My concern as a maintainer is the end result, not how you got there.
Unfortunately, lots of developers don’t understand Git and don’t share my philosophies. As such, you may end up working in an environment where people sneak Husky into the mix. This can have the effect of a executing a bunch of shit that you don’t expect or want.
Option I - Martyrdom
You can cause a big stink and fight the power until the team stops using this trojan horse. Maybe that works for you. Try it out.
Option II - Stoicism
Keeping in line with Stoic ideas like operating within your locus of control, I prefer this option.
Step 1 - Symlink all the hooks you want to use. This has the added benefit of providing a reusable library of hooks for your different projects. You could also try changing core.hooksPath (I haven’t tried this, so I don’t know how Husky works with it). I like to tailor hooks per project, though. Again, no one-size-fits-all solutions.
Step 2 - When you see Husky nonsense, just delete all the hooks that are not links.
find .git/hooks -type f -delete
This option is pretty painless and won’t leave you looking like in self-righteous dick bag. Let everyone keep using Husky. You can undo it quickly.