From gitchain-vercel
Manage Vercel environment variables for GitChain deployments
How this skill is triggered — by the user, by Claude, or both
Slash command
/gitchain-vercel:envThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Manage environment variables for GitChain deployments on Vercel.
Manage environment variables for GitChain deployments on Vercel.
$ARGUMENTS for action:
list — Show all env vars for a projectset [key] [value] — Set/update an env varsync — Sync all required GitChain vars from current config| Variable | Description | Example |
|---|---|---|
GITCHAIN_API_URL | Backend API URL | https://api.gitchain.0711.io |
NEXT_PUBLIC_NAMESPACE | Default namespace | bosch |
NEXT_PUBLIC_TITLE | Site title | GitChain Product Explorer |
API_SECRET | Internal auth | [generated] |
# Environment Variables: [project]
| Variable | Environment | Status |
|----------|-------------|--------|
| GITCHAIN_API_URL | production | ✅ set |
| NEXT_PUBLIC_NAMESPACE | all | ✅ set |
⚠️ Changes require redeployment to take effect.
production, preview, development scopes appropriatelynpx claudepluginhub c-0711/0711-tools --plugin gitchain-vercelConfigures Vercel environments (development, preview, production) with scoped environment variables and branch-specific preview URLs using Vercel CLI and REST API.
Provides expert guidance on Vercel environment variables: .env file hierarchy and load order, secrets management rules, vercel env CLI commands (pull/add/rm/ls), OIDC tokens. Activates on .env patterns and vercel env bash commands.
Manages Vercel projects via CLI with token-based authentication, avoiding interactive login. Useful for deployments, setting environment variables, and CI/CD.