deploy

Automate code deployment with pre-flight checks, production gating, and rollback procedures.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/kirvin/copilot-cli-essentials --skill deploy-kirvin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/kirvin/copilot-cli-essentials/tree/main/plugins/cpe/skills/deploy
Command: npx skills add https://github.com/kirvin/copilot-cli-essentials --skill deploy-kirvin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of deploying code to various environments, ensuring pre-flight checks are performed and providing guidance for production deployments and rollbacks.

Core Features & Use Cases

  • Environment Targeting: Deploy to staging, production, preview, or dev environments.
  • Pre-Flight Checks: Automatically validates working tree, branch status, and CI checks.
  • Production Gate: Enforces checks like branch, CI status, and tag before production deploys.
  • Rollback Guidance: Provides commands to revert changes if a deployment fails.

Quick Start

Use the deploy skill to deploy the current branch to the staging environment.

Frequently Asked Questions about deploy

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

FAQPage Schema
How do I automate code deployment to staging or production environments?

Automate code deployment to staging or production by targeting the specified environment. The process runs pre-flight checks that validate your working tree, branch status, and CI checks before proceeding, ensuring deployment readiness across GitHub Actions, Makefiles, and shell scripts.

What pre-flight checks are required before deploying to production?

Pre-flight checks for production deployment validate the working tree, branch status, and CI checks. A production gate enforces additional requirements, verifying branch rules, CI status, and tags before allowing the deployment to proceed to the production environment.

Can I deploy using GitHub Actions, Makefiles, and npm scripts?

Yes, you can deploy using GitHub Actions, Makefiles, npm scripts, and shell scripts. The deployment mechanism handles various project types by validating readiness and executing the appropriate deployment scripts for your chosen environment target.

How do I rollback a failed production deployment?

Rollback a failed production deployment using provided recovery commands. The deployment process includes rollback guidance that delivers specific commands to revert changes, ensuring you can quickly recover and restore the previous environment state after a deployment failure.

What is the best way to verify a release after deployment?

Verify a release after deployment using post-deploy verification steps. The deployment process includes automated checks that confirm the deployment succeeded and provides recovery steps if the post-deploy verification detects any issues in the target environment.

Does CI status affect production gating during a release?

Yes, CI status directly affects production gating during a release. The production gate enforces checks on branch rules, CI status, and tags, blocking the deployment if CI checks fail or if other pre-flight validations are not met before production.