land-and-deploy

Merge a PR, deploy to production, and run canary health checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy workflows automate the final release steps by merging a PR once CI is green, triggering the deploy to production, and validating production health with canary checks.

Core Features & Use Cases

  • Automatic PR merge after successful CI checks.
  • Canary-based production verification and health checks.
  • Safe promotion and rollback if deployment or health checks fail.
  • Works with standard GitHub PR workflows and can be integrated into existing release pipelines.

Quick Start

Run /land-and-deploy on a ready-to-merge PR to automatically merge, deploy, and verify production health.

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 a GitHub PR merge and deploy to production after CI passes?

Canary health checks validate production deployment health by sending a portion of traffic to the new release and monitoring for issues. If checks fail, the workflow aborts and applies a safe rollback to restore stability.

What happens if a canary health check fails during a production deployment?

Automating your release pipeline requires access to CI status checks, deployment tooling, and health-check mechanisms. These dependencies are necessary to validate readiness and automatically abort if deployment issues are detected.

Do I need access to specific tools to automate PR merges and canary deployments?

You can integrate this automated release workflow into existing standard GitHub PR flows. It bridges the gap between successful CI checks and production deployment by automating the merge, deploy, and canary verification steps.

How does a canary health check work when deploying to production?

To automate a GitHub PR merge and production deploy, you can trigger the workflow on a ready-to-merge PR. It waits for CI status to pass, merges the PR, deploys to production, and validates health using canary checks.