land-and-deploy

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release workflow: merging PRs, waiting for CI, deploying to production, and validating canary health to reduce manual handoffs and risk.

Core Features & Use Cases

  • End-to-end release orchestration: merge, CI wait, deploy, and canary health checks.
  • Post-merge PR handling and production health verification to promote confidence in releases.
  • Use case: when a PR is ready for release, trigger the full ship flow and verify canary signals before production rollout.

Quick Start

Invoke land-and-deploy after a PR merge to automatically merge, deploy, and verify canary 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 merging a pull request, waiting for CI, and deploying to production?

Automate merge and deploy orchestration by merging PRs, waiting for CI checks, deploying to production, and validating canary health to reduce manual handoffs and risk.

What is a canary deployment and how does it verify production health after a PR merge?

Canary deployment validation checks production health signals after merging a PR and deploying to production, ensuring canary metrics are healthy before completing the release rollout.

Can I trigger an end-to-end release workflow automatically after a pull request is ready?

Yes, trigger the full ship flow after a PR is ready for release to automatically merge, wait for CI, deploy, and verify canary signals before production rollout.

Does this release orchestration workflow support CI checks and post-merge promotion flow?

Yes, release orchestration supports CI check waiting and post-merge promotion flow, ensuring production deployment only proceeds after CI passes and PR creation is part of the release process.

What's the best way to reduce manual handoffs when deploying code with a PR workflow?

Use end-to-end release orchestration to merge PRs, wait for CI, deploy to production, and validate canary health, reducing manual handoffs and risk during the release process.

When should I not use automated canary health checks for production deployment?

Automated canary health checks apply specifically to code releases following a PR workflow with CI checks and production deployment, and may not suit workflows lacking these CI and canary validation stages.