项目工具配置指南：GitHub、Vercel、Supabase CLI 安装与验证脚本

project-tooling by alinaqi/claude-bootstrap

99 周安装量

570 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/alinaqi/claude-bootstrap --skill project-tooling

项目引导开发运维命令行工具

🇨🇳中文介绍

项目工具技能

加载方式：base.md

用于项目基础设施管理的标准 CLI 工具。

所需 CLI 工具

在开始任何项目之前，请验证这些工具是否已安装并完成身份验证：

1. GitHub CLI (gh)

# 验证安装
gh --version

# 验证身份验证
gh auth status

# 如果未通过身份验证：
gh auth login

2. Vercel CLI

# 验证安装
vercel --version

# 验证身份验证
vercel whoami

# 如果未通过身份验证：
vercel login

3. Supabase CLI

# 验证安装
supabase --version

# 验证身份验证（检查是否链接到项目或已登录）
supabase projects list

# 如果未通过身份验证：
supabase login

4. Render CLI（可选 - 用于 Render 部署）

# 验证安装
render --version

# 如果使用 Render API 替代：
# 确保在环境中设置了 RENDER_API_KEY

验证脚本

在项目初始化时运行此脚本以验证所有工具：

#!/bin/bash
# scripts/verify-tooling.sh

set -e

echo "验证项目工具..."

# GitHub CLI
if command -v gh &> /dev/null; then
  if gh auth status &> /dev/null; then
    echo "✓ GitHub CLI 已通过身份验证"
  else
    echo "✗ GitHub CLI 未通过身份验证。运行：gh auth login"
    exit 1
  fi
else
  echo "✗ GitHub CLI 未安装。运行：brew install gh"
  exit 1
fi

# Vercel CLI
if command -v vercel &> /dev/null; then
  if vercel whoami &> /dev/null; then
    echo "✓ Vercel CLI 已通过身份验证"
  else
    echo "✗ Vercel CLI 未通过身份验证。运行：vercel login"
    exit 1
  fi
else
  echo "✗ Vercel CLI 未安装。运行：npm i -g vercel"
  exit 1
fi

# Supabase CLI
if command -v supabase &> /dev/null; then
  if supabase projects list &> /dev/null; then
    echo "✓ Supabase CLI 已通过身份验证"
  else
    echo "✗ Supabase CLI 未通过身份验证。运行：supabase login"
    exit 1
  fi
else
  echo "✗ Supabase CLI 未安装。运行：brew install supabase/tap/supabase"
  exit 1
fi

echo ""
echo "所有工具已验证！"

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

Render 设置（基于 API）

# 设置 API 密钥
export RENDER_API_KEY=<your-api-key>

通过 API 的常见操作

# 列出服务
curl -H "Authorization: Bearer $RENDER_API_KEY" \
  https://api.render.com/v1/services

# 触发部署
curl -X POST -H "Authorization: Bearer $RENDER_API_KEY" \
  https://api.render.com/v1/services/<service-id>/deploys

# 获取部署状态
curl -H "Authorization: Bearer $RENDER_API_KEY" \
  https://api.render.com/v1/services/<service-id>/deploys/<deploy-id>

为常见操作添加这些脚本：

{
  "scripts": {
    "verify-tools": "./scripts/verify-tooling.sh",
    "deploy:preview": "vercel",
    "deploy:prod": "vercel --prod",
    "db:start": "supabase start",
    "db:stop": "supabase stop",
    "db:reset": "supabase db reset",
    "db:migrate": "supabase db push",
    "db:types": "supabase gen types typescript --local > src/types/database.ts"
  }
}

使用 Vercel 的 GitHub Actions

# .github/workflows/deploy.yml
name: Deploy

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Deploy to Vercel
        uses: amondnet/vercel-action@v25
        with:
          vercel-token: ${{ secrets.VERCEL_TOKEN }}
          vercel-org-id: ${{ secrets.VERCEL_ORG_ID }}
          vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }}
          vercel-args: ${{ github.ref == 'refs/heads/main' && '--prod' || '' }}

使用 Supabase 的 GitHub Actions

# .github/workflows/migrate.yml
name: Migrate Database

on:
  push:
    branches: [main]
    paths:
      - 'supabase/migrations/**'

jobs:
  migrate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Setup Supabase CLI
        uses: supabase/setup-cli@v1
        with:
          version: latest

      - name: Push migrations
        run: supabase db push
        env:
          SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}
          SUPABASE_DB_PASSWORD: ${{ secrets.SUPABASE_DB_PASSWORD }}

必需：初始化项目时，始终根据技术栈为部署平台连接创建待办事项。

按技术栈选择平台

技术栈	默认平台	所需操作
Next.js / Node.js	Vercel	将 Git 仓库连接到 Vercel
Python (FastAPI, Flask)	Render	将 Git 仓库连接到 Render，获取 API 密钥
静态站点	Vercel 或 Cloudflare Pages	将 Git 仓库连接

Vercel：连接 Git 仓库

当 Vercel 是部署平台时，创建此待办事项：

TODO: 将 Git 仓库连接到 Vercel 以实现自动部署

# 选项 1：通过 CLI
vercel link
vercel git connect

# 选项 2：通过仪表板（推荐用于首次设置）
# 1. 访问 vercel.com/new
# 2. 导入 Git 仓库
# 3. 配置项目设置
# 4. 部署

推送到 main → 生产环境部署
推送到其他分支 → 预览环境部署
PR 自动获得部署预览

Render：连接 Git 仓库（Python）

当 Render 是 Python 项目的部署平台时：

步骤 1：向用户请求 Render API 密钥

在继续之前，请提供您的 Render API 密钥。
从以下地址获取：https://dashboard.render.com/u/settings/api-keys

安全存储 - 我们会将其添加到您的环境中。

步骤 2：创建待办事项

TODO: 从用户获取 Render API 密钥
TODO: 将 Git 仓库连接到 Render
TODO: 配置 Render 服务（Web 服务或后台工作进程）
TODO: 在 Render 上设置环境变量

步骤 3：通过仪表板连接（推荐）

# 1. 访问 dashboard.render.com/create
# 2. 对于 API 选择“Web 服务”，对于异步任务选择“后台工作进程”
# 3. 连接您的 GitHub/GitLab 仓库
# 4. 配置：
#    - 名称：<project-name>
#    - 运行时：Python 3
#    - 构建命令：pip install -r requirements.txt
#    - 启动命令：uvicorn main:app --host 0.0.0.0 --port $PORT

步骤 4：为 CI/CD 存储 API 密钥

# 为 CI/CD 添加到 GitHub 密钥
gh secret set RENDER_API_KEY

# 或者添加到本地环境
echo "RENDER_API_KEY=<your-key>" >> .env

步骤 5：配置 render.yaml（可选 - 基础设施即代码）

# render.yaml
services:
  - type: web
    name: <project-name>-api
    runtime: python
    buildCommand: pip install -r requirements.txt
    startCommand: uvicorn main:app --host 0.0.0.0 --port $PORT
    envVars:
      - key: PYTHON_VERSION
        value: "3.11"
      - key: DATABASE_URL
        fromDatabase:
          name: <project-name>-db
          property: connectionString

databases:
  - name: <project-name>-db
    plan: free

设置部署时添加到项目待办事项：

## 部署设置
- [ ] 创建 Git 仓库 (gh repo create)
- [ ] 选择部署平台 (Vercel/Render/其他)
- [ ] 将 Git 连接到部署平台
- [ ] 配置环境变量
- [ ] 设置 CI/CD 工作流
- [ ] 验证预览部署是否正常工作
- [ ] 配置生产环境域名

❌ 硬编码密钥 - 使用 CLI 环境管理或 GitHub 密钥
❌ 手动部署 - 通过 CI/CD 自动化
❌ 跳过本地 Supabase - 始终先进行本地开发
❌ 直接更改生产数据库 - 使用迁移
❌ 无分支保护 - 要求 PR 审查和 CI 检查
❌ 缺少环境分离 - 保持开发/暂存/生产环境分离

🇺🇸English

Project Tooling Skill

Load with: base.md

Standard CLI tools for project infrastructure management.

Required CLI Tools

Before starting any project, verify these tools are installed and authenticated:

1. GitHub CLI (gh)

# Verify installation
gh --version

# Verify authentication
gh auth status

# If not authenticated:
gh auth login

2. Vercel CLI

# Verify installation
vercel --version

# Verify authentication
vercel whoami

# If not authenticated:
vercel login

3. Supabase CLI

# Verify installation
supabase --version

# Verify authentication (check if linked to a project or logged in)
supabase projects list

# If not authenticated:
supabase login

4. Render CLI (optional - for Render deployments)

# Verify installation
render --version

# If using Render API instead:
# Ensure RENDER_API_KEY is set in environment

Validation Script

Run this at project initialization to verify all tools:

#!/bin/bash
# scripts/verify-tooling.sh

set -e

echo "Verifying project tooling..."

# GitHub CLI
if command -v gh &> /dev/null; then
  if gh auth status &> /dev/null; then
    echo "✓ GitHub CLI authenticated"
  else
    echo "✗ GitHub CLI not authenticated. Run: gh auth login"
    exit 1
  fi
else
  echo "✗ GitHub CLI not installed. Run: brew install gh"
  exit 1
fi

# Vercel CLI
if command -v vercel &> /dev/null; then
  if vercel whoami &> /dev/null; then
    echo "✓ Vercel CLI authenticated"
  else
    echo "✗ Vercel CLI not authenticated. Run: vercel login"
    exit 1
  fi
else
  echo "✗ Vercel CLI not installed. Run: npm i -g vercel"
  exit 1
fi

# Supabase CLI
if command -v supabase &> /dev/null; then
  if supabase projects list &> /dev/null; then
    echo "✓ Supabase CLI authenticated"
  else
    echo "✗ Supabase CLI not authenticated. Run: supabase login"
    exit 1
  fi
else
  echo "✗ Supabase CLI not installed. Run: brew install supabase/tap/supabase"
  exit 1
fi

echo ""
echo "All tools verified!"

GitHub Repository Setup

Create New Repository

# Create and push in one command
gh repo create <repo-name> --private --source=. --remote=origin --push

# Or public:
gh repo create <repo-name> --public --source=. --remote=origin --push

Connect Existing Repository

# If repo exists on GitHub but not linked locally
gh repo clone <owner>/<repo>

# Or add remote to existing local project
git remote add origin https://github.com/<owner>/<repo>.git
git push -u origin main

Repository Settings

# Enable branch protection on main
gh api repos/{owner}/{repo}/branches/main/protection -X PUT \
  -F required_status_checks='{"strict":true,"contexts":["quality"]}' \
  -F enforce_admins=false \
  -F required_pull_request_reviews='{"required_approving_review_count":1}'

# Set default branch
gh repo edit --default-branch main

Vercel Deployment

Link Project

# Link current directory to Vercel project
vercel link

# Or create new project
vercel

Environment Variables

# Add environment variable
vercel env add ANTHROPIC_API_KEY production

# Pull env vars to local .env
vercel env pull .env.local

Deploy

# Deploy to preview
vercel

# Deploy to production
vercel --prod

Supabase Setup

Create New Project

# Create project (interactive)
supabase projects create <project-name> --org-id <org-id>

# Link local to remote
supabase link --project-ref <project-ref>

Local Development

# Start local Supabase
supabase start

# Stop local Supabase
supabase stop

# Reset database (apply all migrations fresh)
supabase db reset

Migrations

# Create new migration
supabase migration new <migration-name>

# Apply migrations to remote
supabase db push

# Pull remote schema to local
supabase db pull

Generate Types

# Generate TypeScript types from schema
supabase gen types typescript --local > src/types/database.ts

# Or from remote
supabase gen types typescript --project-id <ref> > src/types/database.ts

Render Setup (API-based)

Environment

# Set API key
export RENDER_API_KEY=<your-api-key>

Common Operations via API

# List services
curl -H "Authorization: Bearer $RENDER_API_KEY" \
  https://api.render.com/v1/services

# Trigger deploy
curl -X POST -H "Authorization: Bearer $RENDER_API_KEY" \
  https://api.render.com/v1/services/<service-id>/deploys

# Get deploy status
curl -H "Authorization: Bearer $RENDER_API_KEY" \
  https://api.render.com/v1/services/<service-id>/deploys/<deploy-id>

Package.json Scripts

Add these scripts for common operations:

{
  "scripts": {
    "verify-tools": "./scripts/verify-tooling.sh",
    "deploy:preview": "vercel",
    "deploy:prod": "vercel --prod",
    "db:start": "supabase start",
    "db:stop": "supabase stop",
    "db:reset": "supabase db reset",
    "db:migrate": "supabase db push",
    "db:types": "supabase gen types typescript --local > src/types/database.ts"
  }
}

CI/CD Integration

GitHub Actions with Vercel

# .github/workflows/deploy.yml
name: Deploy

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Deploy to Vercel
        uses: amondnet/vercel-action@v25
        with:
          vercel-token: ${{ secrets.VERCEL_TOKEN }}
          vercel-org-id: ${{ secrets.VERCEL_ORG_ID }}
          vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }}
          vercel-args: ${{ github.ref == 'refs/heads/main' && '--prod' || '' }}

GitHub Actions with Supabase

# .github/workflows/migrate.yml
name: Migrate Database

on:
  push:
    branches: [main]
    paths:
      - 'supabase/migrations/**'

jobs:
  migrate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Setup Supabase CLI
        uses: supabase/setup-cli@v1
        with:
          version: latest

      - name: Push migrations
        run: supabase db push
        env:
          SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}
          SUPABASE_DB_PASSWORD: ${{ secrets.SUPABASE_DB_PASSWORD }}

Deployment Platform Setup

REQUIRED : When initializing a project, always create todos for deployment platform connection based on the stack.

Platform Selection by Stack

Stack	Default Platform	Action Required
Next.js / Node.js	Vercel	Connect Git repo to Vercel
Python (FastAPI, Flask)	Render	Connect Git repo to Render, get API key
Static sites	Vercel or Cloudflare Pages	Connect Git repo

Vercel: Connect Git Repository

When Vercel is the deployment platform, create this todo:

TODO: Connect Git repository to Vercel for automatic deployments

Steps:

# Option 1: Via CLI
vercel link
vercel git connect

# Option 2: Via Dashboard (recommended for first setup)
# 1. Go to vercel.com/new
# 2. Import Git repository
# 3. Configure project settings
# 4. Deploy

After connecting:

Push to main → Production deploy
Push to other branches → Preview deploy
PRs get deploy previews automatically

Render: Connect Git Repository (Python)

When Render is the deployment platform for Python projects:

Step 1: Ask user for Render API key

Before proceeding, please provide your Render API key.
Get it from: https://dashboard.render.com/u/settings/api-keys

Store it securely - we'll add it to your environment.

Step 2: Create todos

TODO: Get Render API key from user
TODO: Connect Git repository to Render
TODO: Configure Render service (web service or background worker)
TODO: Set environment variables on Render

Step 3: Connect via Dashboard (recommended)

# 1. Go to dashboard.render.com/create
# 2. Select "Web Service" for APIs, "Background Worker" for async
# 3. Connect your GitHub/GitLab repository
# 4. Configure:
#    - Name: <project-name>
#    - Runtime: Python 3
#    - Build Command: pip install -r requirements.txt
#    - Start Command: uvicorn main:app --host 0.0.0.0 --port $PORT

Step 4: Store API key for CI/CD

# Add to GitHub secrets for CI/CD
gh secret set RENDER_API_KEY

# Or add to local env
echo "RENDER_API_KEY=<your-key>" >> .env

Step 5: Configure render.yaml (optional - Infrastructure as Code)

# render.yaml
services:
  - type: web
    name: <project-name>-api
    runtime: python
    buildCommand: pip install -r requirements.txt
    startCommand: uvicorn main:app --host 0.0.0.0 --port $PORT
    envVars:
      - key: PYTHON_VERSION
        value: "3.11"
      - key: DATABASE_URL
        fromDatabase:
          name: <project-name>-db
          property: connectionString

databases:
  - name: <project-name>-db
    plan: free

Deployment Checklist Template

Add to project todos when setting up deployment:

## Deployment Setup
- [ ] Create Git repository (gh repo create)
- [ ] Choose deployment platform (Vercel/Render/other)
- [ ] Connect Git to deployment platform
- [ ] Configure environment variables
- [ ] Set up CI/CD workflow
- [ ] Verify preview deployments work
- [ ] Configure production domain

Tooling Anti-Patterns

❌ Hardcoded secrets - use CLI env management or GitHub secrets
❌ Manual deployments - automate via CI/CD
❌ Skipping local Supabase - always develop locally first
❌ Direct production database changes - use migrations
❌ No branch protection - require PR reviews and CI checks
❌ Missing environment separation - keep dev/staging/prod separate

Weekly Installs

Repository

alinaqi/claude-bootstrap

GitHub Stars

530

First Seen

Jan 20, 2026

Security Audits

Gen Agent Trust HubPass SocketWarn SnykFail

Installed on

claude-code56

opencode54

gemini-cli49

cursor46

codex46

antigravity43

Azure 升级评估与自动化工具 - 轻松迁移 Functions 计划、托管层级和 SKU

104,900 周安装

项目工具配置指南：GitHub、Vercel、Supabase CLI 安装与验证脚本

🇨🇳中文介绍

项目工具技能

所需 CLI 工具

1. GitHub CLI (gh)

2. Vercel CLI

3. Supabase CLI

4. Render CLI（可选 - 用于 Render 部署）

验证脚本

相关 Skills

GitHub 仓库设置

创建新仓库

连接现有仓库

仓库设置

Vercel 部署

链接项目

环境变量

部署

Supabase 设置

创建新项目

本地开发

迁移

生成类型

Render 设置（基于 API）

环境

通过 API 的常见操作

Package.json 脚本

CI/CD 集成

使用 Vercel 的 GitHub Actions

使用 Supabase 的 GitHub Actions

部署平台设置

按技术栈选择平台

Vercel：连接 Git 仓库

Render：连接 Git 仓库（Python）

部署清单模板

工具反模式

🇺🇸English

Project Tooling Skill

Required CLI Tools

1. GitHub CLI (gh)

2. Vercel CLI

3. Supabase CLI

4. Render CLI (optional - for Render deployments)

Validation Script

GitHub Repository Setup

Create New Repository

Connect Existing Repository

Repository Settings

Vercel Deployment

Link Project

Environment Variables

Deploy

Supabase Setup

Create New Project

Local Development

Migrations

Generate Types

Render Setup (API-based)

Environment

Common Operations via API

Package.json Scripts

CI/CD Integration

GitHub Actions with Vercel

GitHub Actions with Supabase

Deployment Platform Setup

Platform Selection by Stack

Vercel: Connect Git Repository

Render: Connect Git Repository (Python)

Deployment Checklist Template

Tooling Anti-Patterns

最新 Skills