land-and-deploy

Automate release workflows by merging PRs, running CI, deploying, and checking canaries.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/viraatdas/vstack --skill land-and-deploy-viraatdas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/viraatdas/vstack/tree/main/land-and-deploy
Command: npx skills add https://github.com/viraatdas/vstack --skill land-and-deploy-viraatdas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges the PR, waits for CI to complete, triggers the deployment, and verifies production health using canary checks. It takes over after /ship creates the PR, ensuring a streamlined release flow.

Core Features & Use Cases

  • Automates the end-to-end release workflow: merge the PR, run CI, deploy to production, and monitor canaries.
  • Enforces readiness checks before merging and deploying, reducing production risk.
  • Supports both semi-automated and fully automated release scenarios, with safe fallbacks if deployment fails.

Quick Start

Run the land-and-deploy skill to merge the PR, trigger CI, and verify production health via canary checks.

Frequently Asked Questions about land-and-deploy

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

FAQPage Schema
How do I automate merging a PR, running CI, and deploying to production?

To automate a production deploy, this Skill merges the PR, waits for CI to complete, triggers the deployment, and runs canary checks to verify production health. It coordinates steps across version control, CI, and deployment tooling in one workflow.

What happens if a canary check fails during a production deploy?

When a canary check fails during a production deploy, the workflow handles the deployment failure gracefully and provides rollback guidance to help restore production health safely.

How do I verify production health after merging a PR and deploying?

You can verify production health after merging a PR by running canary checks, which monitor the deployment to ensure the release is stable and provide rollback guidance if issues arise.

Can I use this for semi-automated release scenarios or does it require full automation?

This supports both semi-automated and fully automated release scenarios. It enforces readiness checks before merging and deploying, with safe fallbacks if deployment fails, reducing production risk.

When do I need to enforce readiness checks before merging and deploying to production?

You need readiness checks before merging and deploying to production to reduce risk in release engineering. The workflow enforces these checks across version control, CI, and deployment tooling to ensure safe releases.