_setup-github-deploy

Setup GitHub Deploy - Internal helper

Communication

• Detect the user's language from the conversation (the user's own messages, anywhere in the session - not just this invocation: a bare slash command like /bootstrap carries no language signal by itself). If nothing in the conversation gives a signal, fall back to the OS locale (node -e "console.log(Intl.DateTimeFormat().resolvedOptions().locale)") before defaulting to English. ALWAYS reply in that language for every user-facing message: questions, progress, confirmations, summaries, errors - including any example text quoted in this skill, which is illustrative and must be translated, never sent verbatim.
• Use plain, non-technical business language. Never expose internal script names (*.mjs) or jargon; describe actions in human terms.
• When generating user-facing content for the scaffolded project (UI labels, emails, copy), write it in the user's language too.
• Show progress as a short natural-language checklist (in-progress and done states).

You configure GitHub Actions to deploy a Vercel-linked project so that any GitHub collaborator can trigger deployments without a Vercel account.

This is a one-time setup per project. Once done, /add-collab will skip directly to collaborator management.

The caller (/add-collab) has already verified that the setup is missing - do not re-check, go straight to Step 1.

---

Step 1 - Check prerequisites

gh auth status
vercel whoami

Verify the project is linked to Vercel:

test -f .vercel/project.json && echo "linked" || echo "not linked"

If .vercel/project.json does not exist, the project must be linked first. Tell the user:

The project is not linked to Vercel yet. First run vercel link or a full /bootstrap, then run /add-collab again.

Then exit. Otherwise continue.

Step 2 - Get a Vercel token

Vercel tokens cannot be created via CLI - the user must generate one manually.

Tell the user:

So that GitHub Actions can deploy to Vercel on your behalf, it needs a Vercel token.

1. Go to https://vercel.com/account/tokens
2. Click Create Token
3. Give it a meaningful name (for example: github-actions-{project-name})
4. Choose whatever expiration you want (No expiration is fine for a personal project)
5. Click Create and copy the token immediately (you will not be able to see it again afterward)
6. A small window will then open on your machine: paste the token in there, not in our conversation, so it never gets written into this chat.

⚠️ This token will have your Vercel account's permissions. Keep it secret and do not commit it.