skills.rest
timurgaleev
timurgaleevCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

land-and-deploy

Merge PRs, trigger deployments, and validate production health via canaries.

5|Updated Apr 24, 2026
Search Tags:#production#release#merge#deploy#ci#canary#premerge
One-click install
npx skills add https://github.com/timurgaleev/vibestack --skill land-and-deploy-timurgaleev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/timurgaleev/vibestack/tree/main/skills/land-and-deploy
Command: npx skills add https://github.com/timurgaleev/vibestack --skill land-and-deploy-timurgaleev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating a merge, deployment, and production health verification across a PR can be error-prone and slow; this skill automates the end-to-end release flow.

Core Features & Use Cases

  • Automates PR merge, deploy to production, and canary health checks.
  • Enforces pre-merge readiness, CI status, and drift/version checks before landing.
  • Supports rollback guidance if health checks fail and surfaces clear failure reasons.

Quick Start

Invoke the /land-and-deploy command to merge the current PR, trigger the deployment, and validate production 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 PR merge and production deployment in one workflow?▼

Automating PR merge and production deployment involves merging the pull request, triggering the deployment, and running canary health checks. This skill coordinates the end-to-end release flow across GitHub repositories to prevent manual errors.

What pre-merge readiness checks are required before deploying to production?▼

Pre-merge readiness checks inspect CI status, PR state, test results, documentation, and changelog. The workflow enforces drift checks and version gating to ensure deployment readiness before any irreversible actions occur.

How does canary health verification work after a production deployment?▼

Canary health verification validates production health after a deployment by monitoring the canary release. If health checks fail, the workflow surfaces clear failure reasons and provides rollback guidance to restore stability.

Can I use this to enforce safety gates before merging a GitHub pull request?▼

Yes, you can enforce safety gates before merging a GitHub pull request. The workflow inspects CI status and PR state, ensuring all deployment readiness requirements are met before executing the irreversible merge action.

What happens if production health checks fail after an automated deployment?▼

If production health checks fail after an automated deployment, the workflow surfaces clear failure reasons and provides rollback guidance. This ensures you can quickly understand the issue and restore production stability.

Related Skills

Explore More Software Engineering Skills→
gaaschkgaaschk

land-and-deploy

Merge PRs, deploy to production, and verify health via canary checks.

Community
Advanced
JaykaijackJaykaijack

land-and-deploy

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

Community
Advanced
bRRRITSCOLDbRRRITSCOLD
2

ci-cd

Automate CI/CD pipeline creation and management with GitHub Actions.

Community
Advanced
XinheLIUXinheLIU

land-and-deploy

Merge pull requests, deploy to production, and verify canary health checks.

Community
Advanced