deploy

Deploy to Vercel with TypeScript checks, Git status validation, env parity verification, build execution, and post-deploy health checks.

Updated Dec 27, 2025
One-click install
npx skills add https://github.com/Acurioustractor/act-global-infrastructure --skill deploy-acurioustractor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/Acurioustractor/act-global-infrastructure/tree/main/.claude/skills/deploy
Command: npx skills add https://github.com/Acurioustractor/act-global-infrastructure --skill deploy-acurioustractor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a safe, auditable deployment workflow for Vercel that prevents faulty releases by performing pre-flight checks, environment parity verification, build validation, and post-deploy health checks.

Core Features & Use Cases

  • Pre-flight checks: verify TypeScript compilation and code quality before deployment.
  • Env parity & Git hygiene: compare local env vars with Vercel production vars and ensure a clean Git state.
  • End-to-end deployment & health: deploy via Vercel CLI and validate main app and API health endpoints after deployment.
  • Use Case: release a new feature to production after a successful code review and local validation, with automatic health checks to confirm stability.

Quick Start

  1. Ensure you are on the correct feature branch with a clean working tree.
  2. Run pre-flight checks (TypeScript compile and local validation) and resolve any issues.
  3. Push to the remote and deploy using the Vercel CLI: npx vercel --prod.
  4. Run post-deploy health checks by hitting the main app endpoint and API health endpoint to confirm a 200 status code.

Frequently Asked Questions about deploy

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

FAQPage Schema
How do I run pre-flight checks before deploying to Vercel?

Pre-flight checks for Vercel deployments require local TypeScript compilation, code validation, and verifying a clean Git state. You must resolve any compilation errors and ensure your working tree is clean before pushing to the remote branch.

What is environment parity verification in a Vercel CI-CD pipeline?

Environment parity verification compares your local environment variables against Vercel production variables. This pre-flight step prevents faulty releases by ensuring local and production environments match before executing the build and deploy steps.

How do I verify post-deploy health after a Vercel production push?

Post-deploy health verification involves hitting your main app endpoint and API health endpoint after using the Vercel CLI. Confirming a 200 status code from both endpoints validates the release stability and confirms the deployment succeeded.

Do I need the Vercel CLI to deploy a feature branch to production?

Yes, the Vercel CLI is required to execute production deployments through this workflow. You run local TypeScript checks first, push the feature branch to remote, and then trigger the deployment using the command: npx vercel --prod.

Can I deploy to Vercel if my local TypeScript compilation fails?

No, TypeScript compilation is a mandatory pre-flight check to prevent faulty releases. You must resolve any local TypeScript errors and ensure code quality validation passes before pushing your feature branch and running the Vercel deployment.

What's the best way to prevent faulty releases when deploying a Vercel app?

The best way to prevent faulty Vercel releases is combining pre-flight checks, environment parity verification, and post-deploy health checks. This ensures TypeScript compilation passes, local and production env vars match, and API endpoints return 200 status codes.