git --no-verify skips the hooks the team installed

Commits, pushes or merges with --no-verify, which skips the pre-commit and pre-push hooks a team installed on purpose — the formatter, the type check, the secret scanner. It is the most common way a check everyone believes is running turns out not to be. Deliberately does NOT widen to skipping tests in general: mvn -DskipTests package is ordinary work and is asserted as a negative. Known over-match: a -n anywhere in a git commit line, including inside a message. Global flags between git and its subcommand are tolerated (git -C <dir> commit --no-verify, --no-pager, -c k=v), and an absolute tool path such as /usr/bin/git still matches; a flag that itself runs a program is not read. A quoted MENTION is not a use: a search, a git commit -m message, an echo or a curl --data body that only names this command is left alone. That holds only while every shell metacharacter stays inside the quotes, so git commit -m "x" && … is still caught; and the carrier must be the first word, so sudo grep … is not exempt. git commit is NOT one of those carriers here, because this rule's own trigger is a flag of git commit: a commit message that quotes --no-verify still asks.