land-and-deploy

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

Updated Jul 21, 2025
One-click install
npx skills add https://github.com/robertzengcn/aiFetchly --skill land-and-deploy-robertzengcn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/robertzengcn/aiFetchly/tree/main/.agents/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/robertzengcn/aiFetchly --skill land-and-deploy-robertzengcn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, error-prone work of merging release pull requests, waiting for CI pipelines to pass, deploying to production, and verifying deployment health via canary checks, which is typically required after creating a PR with the /ship command.

Core Features & Use Cases

  • End-to-End Deploy Automation: Handles the full post-PR workflow from merge to production verification in one consistent, repeatable process.
  • Context-Aware Execution: Pulls project-specific context like active branch, gstack configuration, and recent project artifacts to tailor the deployment flow to your codebase.
  • Use Case: For engineering teams using gstack, after running /ship to create a release PR, use this Skill to automatically land the PR, wait for all CI checks to pass, deploy to production, and confirm the deployment is healthy without manual step-by-step oversight.

Quick Start

Use the land-and-deploy skill to merge the current release PR, wait for CI to pass, deploy to production, and verify canary health checks are green.

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 pull request merge and production deployment after CI passes?

Automating pull request merge and production deployment requires a tool that handles the end-to-end workflow. This Skill merges release PRs, waits for CI pipelines to pass, deploys to production, and verifies canary health checks automatically.

What is the best way to automate canary health checks after a production deployment?

Automated canary health checks verify deployment health without manual oversight. This Skill executes post-deployment canary verification immediately after landing a release PR and deploying to production, ensuring the release is healthy.

Does this deployment automation tool work with the gstack development toolchain?

Yes, this deployment automation tool works specifically with the gstack development toolchain. It executes immediately after the /ship command creates a release PR, pulling project-specific gstack configuration and recent artifacts to tailor the deployment flow.

How do I wait for CI checks to pass before deploying a release pull request to production?

Waiting for CI checks before deploying a release PR is handled by the automated workflow. This Skill merges the PR, monitors continuous integration pipelines until completion, and only proceeds to production deployment after all checks pass.

Can I automate the entire release workflow from PR creation to deployment verification?

You can automate the entire release workflow from PR creation to deployment verification. Use the /ship command to create the release PR, then this Skill lands the PR, waits for CI, deploys to production, and confirms canary health.

What are the limitations of using automated deployment for release pull requests?

Automated deployment for release PRs is limited to engineering teams using the gstack development toolchain. It requires a release PR created by the /ship command and depends on existing project configuration to execute the context-aware deployment flow.