AGENTS.md says a commit or push never skips the repository's hooks, but in this repository the guard refuses the hook-skipping flag only on git commit and git push. git merge, git rebase, git am and git pull each take the same flag, and the guard allows all four, so for those verbs the rule is prose alone.

AGENTS.md says a commit or push never skips the repository's hooks, but in this repository the guard refuses the hook-skipping flag only on git commit and git push. git merge, git rebase, git am and git pull each take the same flag, and the guard allows all four, so for those verbs the rule is prose alone.

Grounds

• pursued: git's own option tables (git 2.52, each verb's -h) are the authority on which verbs take the hook-skipping flag and what -n means on each: it is that flag on commit and am, the diffstat switch on merge, rebase and pull, dry-run on push, and no-commit on cherry-pick, which has no such flag. A later git that adds the flag to another verb, or gives -n that meaning elsewhere, would show the entry set incomplete.