Ask before pushing

With git connected, a push is a deploy. Get a yes before you push.

From deploy-to-vercel, SKILL.md “Linked + has git remote”.

A push is a deploy

Pick the branch, press Deploy, then answer the agent.

Push straight awayBad
git add . && git commit && git push
Ask, then pushGood
“Want me to proceed?”
# Ask first:
# "This project is connected to Vercel via git. I can commit and
#  push to trigger a deployment. Want me to proceed?"

# Only after a yes:
git add .
git commit -m "deploy: <description of changes>"
git push

Why it matters, pros and cons

Why it matters

A push publishes commits and starts a build. On the production branch it is a production deploy.

Pros

  • The user decides what ships and when.
  • No surprise commits in their history.
  • One question, then no more confirmations.

Cons

  • One more round-trip before each deploy.
  • Standing approval (CI, a bot) can skip it.