Skill

role-fullstack:deployment-workflow

Set up deployment workflows for Vercel, Netlify, Railway, Render, and Docker. Covers preview environments per PR, database migrations in CI (expand-contract pattern), environment variable validation, health check endpoints, and rollback procedures. Use when configuring deployment pipelines, managing env vars across stages, or establishing rollback runbooks.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin role-fullstack

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash

Preview

- Configuring a deployment pipeline for a new project

Supporting Assets

references/health-checks-rollback.mdreferences/migrations-env-vars.mdreferences/platform-selection.md

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

157.6k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

157.6k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

role-fullstack:deployment-workflow

When to use

Configuring a deployment pipeline for a new project

Setting up preview environments per pull request

Managing environment variables across development, staging, and production

Running database migrations safely in CI without downtime

Adding health check endpoints for load balancer routing

Establishing rollback procedures before the first production incident

Core principles

Platform matches project shape — Vercel for edge-first Next.js, Railway/Render for fullstack with databases, Fly.io for global edge

Migrations before deploy, never after — run prisma migrate deploy as a CI step preceding the deploy step, never during

Expand-contract for zero downtime — add column → backfill → update code → drop old column across three separate deploys

Validate env vars at startup — use @t3-oss/env-nextjs or zod to crash fast with a clear message rather than fail silently at runtime

Health check is not optional — every deployed service needs /api/health returning 200/503; load balancers depend on it

Reference Files

references/platform-selection.md — comparison table for Vercel, Netlify, Railway, Render, Fly.io; Vercel setup steps; multi-stage Dockerfile for Node.js; Docker-based preview environments per PR

references/migrations-env-vars.md — CI migration steps, expand-contract pattern walkthrough, env var management with secrets managers, common pitfalls

references/health-checks-rollback.md — health check endpoint implementation, liveness vs readiness probes, rollback procedures for Vercel/Docker/database, incident runbook checklist

Deployment Workflow

When to use

Configuring a deployment pipeline for a new project
Setting up preview environments per pull request
Managing environment variables across development, staging, and production
Running database migrations safely in CI without downtime
Adding health check endpoints for load balancer routing
Establishing rollback procedures before the first production incident

Core principles

Platform matches project shape — Vercel for edge-first Next.js, Railway/Render for fullstack with databases, Fly.io for global edge
Migrations before deploy, never after — run prisma migrate deploy as a CI step preceding the deploy step, never during
Expand-contract for zero downtime — add column → backfill → update code → drop old column across three separate deploys
Validate env vars at startup — use @t3-oss/env-nextjs or zod to crash fast with a clear message rather than fail silently at runtime
Health check is not optional — every deployed service needs /api/health returning 200/503; load balancers depend on it

Reference Files

references/platform-selection.md — comparison table for Vercel, Netlify, Railway, Render, Fly.io; Vercel setup steps; multi-stage Dockerfile for Node.js; Docker-based preview environments per PR
references/migrations-env-vars.md — CI migration steps, expand-contract pattern walkthrough, env var management with secrets managers, common pitfalls
references/health-checks-rollback.md — health check endpoint implementation, liveness vs readiness probes, rollback procedures for Vercel/Docker/database, incident runbook checklist