SkillHub ClubRun DevOpsDevOpsFrontend

deploy-automation

This skill automates deployment to multiple platforms (Vercel, Fly.io, Cloudflare, Netlify) based on project templates. It handles platform-specific configuration, runs pre-deploy checks, and returns production URLs. Supports Next.js, FastAPI, Hono, and static sites.

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars

Hot score

Updated

March 20, 2026

Overall rating

A7.3

Composite score

4.8

Best-practice grade

S96.0

Install command

npx @skill-hub/cli install timequity-plugins-deploy-automation

deploymentvercelcloudflareautomation

Repository

timequity/plugins

Skill path: vibe-coder/skills/deploy-automation

Open repository

Best for

Primary workflow: Run DevOps.

Technical facets: DevOps, Frontend.

Target audience: Developers who need to deploy web applications to cloud platforms without memorizing platform-specific commands.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: timequity.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

Install deploy-automation into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/timequity/plugins before adding deploy-automation to shared team environments
Use deploy-automation for devops workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: deploy-automation
description: |
  One-click deploy to production. User just says "deploy".
  Use when: user wants to publish their app.
  Triggers: "deploy", "publish", "go live", "опубликуй".
---

# Deploy Automation

Deploy to production with one command.

## Platform Selection

Based on template:

| Template | Platform | Why |
|----------|----------|-----|
| nextjs-supabase | Vercel | Native Next.js support |
| fastapi-postgres | Fly.io | Docker + persistent DB |
| hono-drizzle | Cloudflare | Edge-native |
| landing-page | Netlify/Vercel | Static 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:

```bash
# 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:
- "Add domain" → configure DNS
- Auto-SSL via platform
- "✅ Live at https://yourdomain.com"