land-and-deploy

Automate merge, deploy, and production health validation workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end land-and-deploy workflow, ensuring merges occur only after CI green and that post-merge production health is verified against dashboards and error budgets. This approach provides a formalized, auditable path from PR to production, reducing deployment risk and increasing reproducibility.

Core Features & Use Cases

  • Gate merges on green CI and trigger post-merge validation against production telemetry.
  • Coordinate merge, deploy, and verification steps, including canary checks and rollback readiness.
  • Provide an audit trail by recording merge commits, deploy timestamps, and health check results.

Quick Start

Initiate land-and-deploy by ensuring CI is green, merging the PR, and validating production health via dashboards and error budgets.

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 merges only after CI passes and verify production health?

Yes, you can gate PR merges on green CI and trigger post-merge validation. This Skill coordinates merge, deploy, and verification steps, including canary checks and rollback readiness, ensuring changes touching shared infrastructure or data migrations are safely deployed.

What is a land and deploy workflow for shared infrastructure changes?

A land and deploy workflow merges PRs after CI green and validates production health via dashboards and error budgets. It is specifically needed for changes touching shared infrastructure, data migrations, or authentication where pre-merge checks are insufficient and post-merge verification is required.

How do I maintain an audit trail of merge commits, deploy timestamps, and health results?

To maintain an audit trail of merge commits, deploy timestamps, and health results, this Skill records every merge commit, deploy timestamp, and health check result during the land-and-deploy workflow. This provides a formalized, auditable path from PR to production.

Does this land-and-deploy approach support canary checks and rollback readiness?

Yes, this land-and-deploy approach supports canary checks and rollback readiness. It coordinates these verification steps alongside merge and deploy actions, applying post-merge validation against production telemetry to reduce deployment risk and increase reproducibility.

When should I use post-merge validation instead of pre-merge CI checks?

You should use post-merge validation when changes touch shared infrastructure, data migrations, or authentication. In these cases, pre-merge checks are insufficient, and this Skill validates production health against dashboards and error budgets after the PR merge.