deployment

Deploy code to production via Vercel and GitHub Actions with automated checks and rollbacks.

Updated Mar 1, 2026

Search Tags:#ci/cd #deployment #rollback #production #github actions #vercel

Ready to run

npx skills add https://github.com/mqzkim/trading --skill deployment-mqzkim

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deployment
Source: https://github.com/mqzkim/trading/tree/main/.agents/skills/deployment
Command: npx skills add https://github.com/mqzkim/trading --skill deployment-mqzkim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of deploying code changes to production environments, ensuring safety and reliability through automated checks and rollbacks.

Core Features & Use Cases

Vercel Deployment: Integrates with Vercel for seamless Preview and Production deployments.
CI/CD Integration: Works with GitHub Actions to perform type checks, tests, and linting before deployment.
Automated Rollbacks: Automatically reverts deployments if post-deployment smoke tests fail.
Use Case: Deploying a new feature to production by specifying the branch name, with automated checks and a rollback mechanism in place if issues arise.

Quick Start

Deploy the current branch to production.

Frequently Asked Questions about deployment

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

FAQPage Schema

How do I deploy a specific branch to production using GitHub Actions and Vercel?▼

To deploy a specific branch to production, this skill automates Vercel deployments triggered through GitHub Actions, running type checks, tests, and linting before safely releasing your code changes to the production environment.

Can I automatically rollback a production deployment if smoke tests fail?▼

Yes, automated rollbacks are supported. If post-deployment smoke tests detect issues, the system automatically reverts the production deployment to ensure reliable software delivery and minimize downtime.

What is the safest way to automate CI/CD rollbacks for production environments?▼

The safest way to automate CI/CD rollbacks is using a deployment skill that integrates automated checks, post-deployment smoke tests, and automatic reversion mechanisms within your GitHub Actions workflow before finalizing production releases.

Do I need to configure smoke tests for Vercel preview deployments?▼

Yes, smoke tests are required. The skill handles post-deployment smoke tests for both preview and production Vercel deployments to verify stability and trigger automatic rollbacks if critical issues arise.

Does this deployment skill support deploying pull requests to Vercel?▼

Yes, deploying pull requests is supported. The skill seamlessly integrates with Vercel to handle both preview deployments for pull requests and full production deployments for specific branches.

Why are automated type checks and linting necessary before deploying to production?▼

Automated type checks and linting are necessary before production deployment to catch code errors early. The skill runs these checks via GitHub Actions to ensure only verified, stable code changes reach the production environment.