land-and-deploy

Merge PRs, run CI checks, deploy, and verify production via canary tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy workflow merges the PR, waits for CI, deploys, and verifies production health via canary checks. It takes over after /ship creates the PR to ensure a safe, auditable production release.

Core Features & Use Cases

  • End-to-end release orchestration: merges PRs, runs CI checks, handles canary verification, and promotes canary or production deployments.
  • Guarded deployment workflow: provides pre-merge readiness and post-merge validation to reduce prod risk.
  • Quick Start: Activate the land-and-deploy flow to streamline the final release steps from land through ship to production, with safety checks and rollback guidance.

Quick Start

Invoke the land-and-deploy skill via /land-and-deploy to merge the PR, run through CI checks, perform deployment, and verify production health with canary tests.

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 merging and production deployment in one workflow?

Automating PR merge and production deploy requires orchestrating CI pipelines, canary checks, and production verification. This workflow merges your PR, waits for CI feedback, deploys to production, and verifies health via canary tests for a safe release.

What is a canary check in a production deploy pipeline?

A canary check in a production deploy pipeline verifies production health by routing a portion of traffic to the new release. This workflow performs canary verification post-merge to ensure stability before promoting a full production deployment.

Do I need an existing pull request to run an end-to-end land and deploy workflow?

Yes, an end-to-end land and deploy workflow requires an existing pull request for the current branch. It needs GitHub-based projects with active CI pipelines and a deploy pipeline to coordinate pre-merge readiness and post-merge validation.

How do I verify production health after merging a pull request?

To verify production health after merging a pull request, the workflow runs post-merge validation and canary checks. It coordinates deploy verification steps and post-deploy signaling to confirm stability and reduce production risk.

Can I do a dry run for my first production deployment?

Yes, you can do a dry run for your first production deployment. The workflow guides dry runs for initial deployments, providing pre-merge readiness checks and post-merge validation to ensure a safe, auditable production release.

What are the limitations of automating PR merge and canary deployment?

This automated PR merge and canary deployment workflow is limited to GitHub-based projects with existing CI pipelines and requires an active PR. It cannot execute without CI feedback and a configured deploy pipeline for production releases.