Deploy

Deploy Skill

Step 1: Identify the project

Determine which project to deploy from cwd or user's message. If ambiguous, ask.

Step 2: Identify the platform

Common deployment targets:

Vercel (frontend)

# Auto-deploy via git push
git push origin main       # or preview/production branch

# Manual deploy
vercel --token $VERCEL_TOKEN

Render (backend)

# Trigger deploy via API
curl -s -X POST "https://api.render.com/v1/services//deploys" \
  -H "Authorization: Bearer $RENDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"clearCache":"clear"}'

Docker (self-hosted)

# Rebuild and restart container
docker compose build && docker compose up -d

# Or just restart
docker restart 

Supabase Edge Functions

supabase functions deploy 

Pre-deploy checklist

1. Run git diff to review what's being deployed
2. Run build locally: npm run build or equivalent
3. Run tests if they exist
4. Check for uncommitted .env changes (never commit secrets)

Post-deploy verification

1. Check the live URL loads correctly
2. For API backends: hit the health endpoint (/api/health)
3. Check deploy logs for errors
4. Verify key functionality works end-to-end

Project-specific notes

Check CLAUDE.md in the project root for project-specific deploy steps, branch strategies, and gotchas.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: floomhq
• Source: floomhq/moto
• License: MIT
• Homepage: https://github.com/floomhq/moto#readme

Install and usage instructions live in the source repository linked above.