push-check

A push feels finished before it is. The checks pass, the files look fine, and the faults turn up when someone else downloads the work: a leaked key, a link to a file that is not there, a setup step that only works on your machine. None of it is hard to find. Nothing looked for it.

A push is a sequence, not a command. Every step below runs, in order, before git push. The step that "obviously will pass" is the one that catches something.

Talk to the user in plain English the whole way through. They may not know git. Say what you found and what you did about it, never which command printed it.

Step 1. Say what is about to leave