deploy-runbook

Provides per-platform deployment checklists and smoke-test rituals for Vercel, Render, Railway, Convex, and Atlas.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/vinodkrishna221/Q-Trace --skill deploy-runbook-vinodkrishna221
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-runbook
Source: https://github.com/vinodkrishna221/Q-Trace/tree/main/.agents/skills/deploy-runbook
Command: npx skills add https://github.com/vinodkrishna221/Q-Trace --skill deploy-runbook-vinodkrishna221

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams shipping web apps under deadline pressure repeatedly hit the same deployment failures: missing environment variables, wrong start commands, CORS misconfigurations, cold starts, and last-minute deploy freezes. This Skill turns those recurring 2am failures into ordered, tickable checklists so deploys stay boring, early, and continuous. ## Core Features & Use Cases - Per-Platform Checklists: Ordered deploy steps for Vercel (Next.js), Render/Railway (FastAPI and Node), Convex, and MongoDB Atlas, each line targeting a known classic failure. - Smoke Ritual: A 3-minute post-merge verification loop (seed, boot, click the demo path, check for errors) with a red-smoke merge freeze rule. - Pre-Warm & Freeze Calendar: A T-10 minute pre-warm routine to kill free-tier cold starts before demos, plus a T-5h to T-45m freeze schedule for hackathon endgames. - Use Case: During a hackathon, after every merge to main, run the smoke ritual to confirm the demo path still works, then follow the freeze calendar so the final deploy lands before build queues spike. ## Quick Start Ask the AI to walk you through the deploy-runbook checklist for deploying your Next.js frontend to Vercel and FastAPI backend to Render, then run the smoke ritual.

Frequently Asked Questions about deploy-runbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a Next.js app to Vercel without common failures?

Import the repo with framework auto-detection, set every NEXT_PUBLIC_* and server env var before the first deploy, verify next build passes locally, and configure remote image patterns. After deploying, test a dynamic route and a server action, not just the homepage.

How do I deploy a FastAPI backend to Render or Railway?

Set the start command to uvicorn app.main:app --host 0.0.0.0 --port $PORT, ensure a /health route exists, sync env vars from .env.example, and update CORS with the Vercel frontend URL. Expect 30-60 second cold starts on free tiers.

Why do Convex environment variables not work after deploy?

Convex action env vars must be set in the Convex dashboard, not in a local .env file, which is a classic silent failure. After setting them, switch NEXT_PUBLIC_CONVEX_URL on Vercel and run the seed mutation against production.

What is a smoke test ritual after merging to main?

The smoke ritual is a 3-minute post-merge check: seed the data, boot or deploy, click through the demo path, and verify no console errors, no 500s, working LLM calls, and realtime updates. A red smoke result freezes merges until green.

How do I avoid cold starts before a live demo?

Run the pre-warm ritual 10 minutes before pitching: hit every free-tier URL, make one scripted LLM call to warm the key, open all demo tabs, verify feature flags, and refresh the seed if state drifted. Keep a backup video queued.

When should I freeze deploys before a hackathon deadline?

Follow the freeze calendar: risky-feature freeze at T-5h, feature freeze at T-3h, merge freeze at T-2h, and deploy freeze at T-90m, since build queues spike when many teams ship simultaneously. Refresh the final backup video at T-45m.