add-collab

Add Collab - Manage GitHub collaborators

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 manage the GitHub collaborators of the current project.

This skill assumes the project is hosted on GitHub and deployed via Vercel. The first time it runs on a new project, it sets up GitHub Actions as the deploy mechanism (via the _setup-github-deploy helper). On subsequent runs, it skips straight to collaborator management.

---

Step 1 - Detect whether GitHub Actions deploy is already configured

Run two checks in parallel:

# Check 1 - workflow file exists locally
test -f .github/workflows/deploy.yml && echo "workflow:yes" || echo "workflow:no"

# Check 2 - the 3 Vercel secrets exist on GitHub
gh secret list 2>/dev/null | awk '{print $1}'

The setup is complete only if all 4 conditions are true:

• .github/workflows/deploy.yml exists locally
• Secret VERCEL_ORG_ID is listed
• Secret VERCEL_PROJECT_ID is listed
• Secret VERCEL_TOKEN is listed

If any of these is missing, the setup is incomplete → invoke the _setup-github-deploy internal skill, wait for it to complete, then continue to Step 2.