Claude-skill-registry deploy-automation

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/deploy-automation" ~/.claude/skills/majiayu000-claude-skill-registry-deploy-automation && rm -rf "$T"
manifest: skills/data/deploy-automation/SKILL.md
source content

Deploy Automation

Deploy to production with one command.

Platform Selection

Based on template:

TemplatePlatformWhy
nextjs-supabaseVercelNative Next.js support
fastapi-postgresFly.ioDocker + persistent DB
hono-drizzleCloudflareEdge-native
landing-pageNetlify/VercelStatic hosting

Deploy Process

Vercel (Next.js)

  1. Check Vercel CLI installed
  2. Set environment variables
  3. vercel --prod
  4. Return production URL

Fly.io (FastAPI)

  1. Generate Dockerfile if missing
  2. Create fly.toml
  3. Set secrets
  4. fly deploy
  5. Return production URL

Cloudflare (Hono)

  1. Configure wrangler.toml
  2. Set secrets
  3. wrangler deploy
  4. Return workers.dev URL

Netlify (Static)

  1. Build static files
  2. netlify deploy --prod
  3. Return production URL

Pre-Deploy Checks

  • All tests pass
  • No console.log
  • Environment variables set
  • Build succeeds
  • No security issues

Environment Variables

Template for each platform:

# Supabase
NEXT_PUBLIC_SUPABASE_URL=
NEXT_PUBLIC_SUPABASE_ANON_KEY=
SUPABASE_SERVICE_ROLE_KEY=

# PostgreSQL
DATABASE_URL=
SECRET_KEY=

# General
NODE_ENV=production

User Experience

User: "Deploy this"

  1. "Deploying to [platform]..."
  2. Run pre-deploy checks
  3. Build production
  4. Deploy
  5. "✅ Live at https://your-app.vercel.app"

Custom Domains

After initial deploy: