land-and-deploy

Merge PRs, wait for CI, deploy, and verify production health in GitHub workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy coordinates merge, CI wait, deployment, and production health validation into a single, end-to-end workflow.

Core Features & Use Cases

  • Automates the end-to-end release flow: merge PRs, wait for CI, run deployment, and verify production health with canary checks.
  • Handles typical PR-based deploys in GitHub workflows, including pre-merge validations and post-deploy health verification.
  • If issues arise, can revert or halt the deployment to protect production.

Quick Start

Invoke /land-and-deploy to merge the PR, deploy to production, and verify health with 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 PR merge and production deployment in a single workflow?▼

Automating PR merge and production deployment involves coordinating merge, CI wait, deployment, and health validation into a single end-to-end workflow. This process handles PR-based deploys in GitHub workflows, including pre-merge validations and post-deploy health verification.

What is a canary check and how does it protect production during deployment?▼

A canary check is a post-deploy health validation step that monitors production stability after a release. If issues arise during this check, the deployment can automatically revert or halt to protect production from widespread failure.

Do I need an authenticated GitHub CLI to merge and deploy pull requests?▼

Yes, you need an authenticated GitHub CLI to merge and deploy pull requests. The workflow also requires access to the repository and a configured deploy pipeline to detect the PR and follow the configured base branch rules.

What's the best way to revert a deployment if production health verification fails?▼

The best way to revert a failed deployment is to use an end-to-end workflow that includes post-deploy health verification. When production health validation detects issues, the workflow can automatically halt or revert the deployment.

Can I trigger a production release from a specific pull request number?▼

Yes, you can trigger a production release from a specific pull request number. The workflow detects the PR from the current branch or a provided URL or PR number to initiate the merge, CI wait, and deployment sequence.

Does the deployment workflow wait for CI checks to pass before merging?▼

Yes, the deployment workflow waits for CI checks to pass. It coordinates pre-merge validations and waits for CI completion before proceeding with the deployment and subsequent production health verification.