land-and-deploy

Merge PRs, wait for CI, deploy to production, and verify canary health.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/nhattran998/personal-athlete-agent --skill land-and-deploy-nhattran998
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/nhattran998/personal-athlete-agent/tree/main/.agents/skills/gstack-land-and-deploy
Command: npx skills add https://github.com/nhattran998/personal-athlete-agent --skill land-and-deploy-nhattran998

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land-and-deploy streamlines the end-to-end process of merging PRs, waiting for CI, deploying to production, and verifying production health via canary checks, reducing manual handoffs and deployment risk.

Core Features & Use Cases

  • End-to-end land-and-deploy workflow: merges PRs, waits for CI, deploys, and validates health with canaries.
  • Seamless handoff to production by taking over after /ship, enabling fast, reliable releases.
  • Use cases include multi-branch release coordination, automated rollouts with canaries, and production health validation in CI/CD pipelines.

Quick Start

Merge a PR, trigger CI, and deploy to production with canary health verification.

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 PR merge, CI, and production deploy in one workflow?

Automate the land-and-deploy workflow by merging PRs, waiting for CI, deploying to production, and verifying canary health. It coordinates with the /ship flow and creates or updates the PR to hand off production responsibly.

What are canary checks and how do they validate production health after deploy?

Canary checks validate production health after deploy by monitoring the newly released version for errors. This workflow automates these checks to reduce manual verification and deployment risk.

Do I need a gstack-enabled environment to run automated land and deploy workflows?

Yes, you need a configured Git repository with CI/CD hooks and a gstack-enabled environment. These prerequisites orchestrate the merge, CI wait, deploy, and canary verification steps.

How does the land-and-deploy workflow handle multi-branch release coordination?

It handles multi-branch release coordination by taking over after the /ship flow. The workflow merges branches, triggers CI, deploys to production, and creates or updates PRs for responsible handoffs.

Can I use this workflow for automated rollouts with canary verification in CI/CD pipelines?

Yes, the workflow supports automated rollouts with canaries and production health validation in CI/CD pipelines. It streamlines merging, CI verification, deployment, and health checks.

What are the limitations of automating production deployments with canary checks?

Limitations include the strict requirement for a configured Git repository with CI/CD hooks and a gstack-enabled environment. Without these dependencies, the workflow cannot orchestrate the automated deploy and canary verification steps.