Don't just commit, pre-commit!
Look, I get it, you're a consummate professional. You just joined a team that's sponsored by Nike but your bread is buttered by Adidas . Thing is, it's a team sport: on this team when you're out there on the field/pitch/court, please wear the Nikes. That's just how it goes. Best we can do? Commit to our team Nikes but tape over the swooshes. Just don't tell 'em I said so, deal? 🤝
It's no different on a tech team. Sure, you're as flawless as flawless gets with the code; a demigod on the command-line; a virtuoso with the vim motions. You don't make mistakes! You don't understand why you have to spend a couple moments letting some git hooks run on local before you can push your — obviously bug-free — code up for the PR.
By the time you're brushing up against git hooks, I promise you some pains have been felt upstream. Unless of course someone in the org just read a book over the weekend and is now implementing every possible Agile philosophy wholesale. Ouch! In addition, you likely have non-dev collaborators and this is one part of a larger picture.
