skills.rest
GenEducation
GenEducationOFFICIAL
Explore all skills by this author →
GitHub

land-and-deploy

Merge a pull request, wait for CI and deployment, and verify production health with canary checks.

Updated Mar 30, 2026
Search Tags:#github#release#merge#deploy#ci#canary
One-click install
npx skills add https://github.com/GenEducation/GenedUIProject --skill land-and-deploy-geneducation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/land-and-deploy
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill land-and-deploy-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill takes a ready pull request from merge to production without the usual manual babysitting, so you do not have to chase CI, watch deploy queues, and then guess whether the release actually worked.

Core Features & Use Cases

  • Merge automation: Detects the target branch or PR, merges it efficiently, and handles the release handoff.
  • Deploy waiting and readiness checks: Watches CI and deployment progress, with gates that stop the process when something is not ready.
  • Post-deploy verification: Confirms production health with canary-style checks and optional URL-based validation after the deploy lands.
  • Use case: A developer finishes a feature, runs the Skill, and gets a clear production verdict instead of juggling GitHub tabs and deployment status pages.

Quick Start

Ask the land-and-deploy skill to merge the current pull request and verify the deployed site.

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 merging a pull request and waiting for CI deployment?▼

You can automate merging a pull request and waiting for CI deployment by running a workflow that merges the PR, tracks the full deploy path, and confirms production health without manual babysitting.

What is canary verification in a release workflow?▼

Canary verification in a release workflow is a post-deploy check that confirms production health against a live URL after shipping code, ensuring the deployed site responds correctly before declaring release success.

Does this deployment automation require specific branch or PR detection?▼

Yes, this deployment automation requires branch and PR detection to resolve the base branch, apply readiness gates, track deployment progress, and execute post-deploy verification against a production URL.

What is the best way to stop a deploy if CI is not ready?▼

The best way to stop a deploy if CI is not ready is to use readiness gates that monitor CI and deployment progress, automatically halting the merge and release handoff process when checks fail.

Can I verify production health automatically after a GitHub merge?▼

You can verify production health automatically after a GitHub merge by running a workflow that applies canary-style checks and optional URL-based validation immediately after the deploy lands.

What happens if the post-deploy canary check fails?▼

If the post-deploy canary check fails, the process provides a clear production verdict indicating the site is unhealthy, stopping the release workflow from proceeding further without manual investigation.

Related Skills

Explore More Software Engineering Skills→
nsheapsnsheaps
3

update-branch

Synchronize feature branches with their PR base using git and gh.

Community
Advanced
MissTullyMissTully

land-and-deploy

Automate PR merge, CI wait, and production canary verification.

Community
Advanced
ajsai47ajsai47
11

land-and-deploy

Merge GitHub pull requests and verify production health after deployment.

Community
Advanced
jerrywu001jerrywu001
6

land-and-deploy

Merge GitHub pull requests, wait for CI and deployment, and verify production health with canary checks.

Community
Advanced