run-and-operate

Guides running, deploying, releasing, and rolling back a Next.js app on Vercel.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/MarineTeam/fable-video --skill run-and-operate-marineteam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-and-operate
Source: https://github.com/MarineTeam/fable-video/tree/main/.claude/skills/run-and-operate
Command: npx skills add https://github.com/MarineTeam/fable-video --skill run-and-operate-marineteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operating a Next.js app deployed to Vercel involves scattered knowledge: how to run it locally, how merges become live deploys, where logs land, how to cut a release, and how to roll back safely. This Skill consolidates that operational runbook into one place so you never guess at deploy mechanics or lose production data during a rollback. ## Core Features & Use Cases - Local run and build: Documents npm run dev behavior (including the expected 500s without env vars), the exact dummy-env one-liner for reproducing CI's npm run build locally, and npm start for production-mode serving. - Deploy and release runbook: Explains the Vercel auto-deploy model from main, CI as a status check, manual data migrations, the CHANGELOG → version bump → git tag → GitHub Release flow, and instant rollback via the Vercel dashboard. - Output and incident map: Tables showing where every kind of output lands (terminal, Vercel Logs, browser console, GitHub Actions, Sentry) plus warnings that Redis is shared production data unaffected by rollbacks. - Use Case: You merged a PR and the site broke in production. Use this Skill to find the runtime logs in Vercel, decide whether to roll back via Promote to Production, and remember that reverting an env var also requires a redeploy. ## Quick Start Ask the AI to walk you through deploying the latest main branch to production and verifying the deploy succeeded using this runbook.

Frequently Asked Questions about run-and-operate

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

FAQPage Schema
How do I deploy a Next.js app to Vercel from GitHub?

Vercel auto-deploys every push to the main branch of the connected GitHub repository. Merge a PR to main after CI passes, and Vercel builds and deploys it automatically with no manual deploy step.

How do I roll back a bad Vercel deployment?

Open the Vercel dashboard, go to Deployments, find the last-known-good deployment, and select Promote to Production or Rollback. Note this does not roll back Redis data, and reverting an env var also requires a redeploy.

Why does my Next.js dev server return 500 on every route?

In this repo, every route 500s without environment variables because the proxy.js middleware runs Auth0 session handling on all requests. Set AUTH0_DOMAIN, AUTH0_CLIENT_ID, AUTH0_SECRET, and related vars in .env.local to get past it.

Do Vercel environment variable changes apply immediately?

No. Changing, adding, or removing a Vercel environment variable does nothing to already-running deployments. You must redeploy from the Deployments page for the new values to take effect.

Why does my build pass in CI but fail on Vercel?

Vercel runs its own npm install at deploy time, and without a committed lockfile its fresh resolution of caret ranges can differ from what CI tested. Suspect dependency version drift first when CI and Vercel disagree.

When should I not use this runbook?

Do not use it to decide whether a change is safe to merge, to diagnose a runtime symptom like a 502 or login loop, or to add environment variables. Those belong to the change-control, debugging-playbook, and environment-and-config skills respectively.