land-and-deploy

Merge approved pull requests and verify production health after deployment.

2|1|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill land-and-deploy-code-saurabh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/CODE-SAURABH/OpenSkills/tree/main/land-and-deploy
Command: npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill land-and-deploy-code-saurabh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents approved changes from being treated as successfully shipped without verifying the merge, CI pipeline, deployment, production health, and feature behavior.

Core Features & Use Cases

  • Pre-Land Validation: Confirms approvals, green CI, deployment readiness, rollback plans, feature flags, and migration safety before merging.
  • Deployment Monitoring: Guides monitoring across GitHub Actions, Vercel, Railway, Render, Kubernetes, AWS ECS, and Heroku.
  • Production Verification: Checks health endpoints, error rates, latency, critical user paths, database migrations, and feature-specific behavior.
  • Rollback Readiness: Provides decision criteria and platform-specific rollback procedures when health checks, smoke tests, or error metrics fail.
  • Use Case: After a pull request is approved, use this Skill to merge it, monitor CI and deployment completion, validate production health, confirm the feature works, and document the release.

Quick Start

Use the land-and-deploy skill to merge the approved pull request, monitor its deployment, verify production health, and record the release evidence.

Frequently Asked Questions about land-and-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify production changes after merging an approved pull request?

To verify production changes after merging an approved pull request, check health endpoints, monitor error rates and latency, execute smoke tests, validate critical user paths, and confirm feature-specific behavior to ensure deployment stability.

What does a release workflow need before executing a production deployment?

A production deployment requires pre-land validation confirming pull request approvals, green CI status, deployment readiness, active rollback plans, feature flags, and migration safety before executing the merge.

How do I monitor CI pipelines and deployments across platforms like Vercel, Kubernetes, and AWS ECS?

Monitor CI pipelines and deployments across Vercel, Kubernetes, AWS ECS, Railway, Render, and Heroku by tracking deployment status, verifying platform-specific health checks, and observing production metrics post-merge.

Does this deployment workflow support automated rollback procedures when health checks fail?

Yes, the deployment workflow supports automated rollback procedures by providing decision criteria and platform-specific recovery steps to execute when production health checks, smoke tests, or error metrics fail.

How do I document a release after verifying production health and feature behavior?

Document a release after verifying production health by recording deployment evidence, capturing health check results, noting smoke test outcomes, and logging feature validation status to maintain post-deploy documentation.