skills.rest
Kakarottoooo
KakarottooooCOMMUNITY
Explore all skills by this author →
GitHub

land-and-deploy

Merge pull requests, wait for CI, and validate production canary health.

Updated Mar 17, 2026
Search Tags:#release-management#ci-cd#canary#github-cli#pr-merge#land-and-deploy
One-click install
npx skills add https://github.com/Kakarottoooo/onegent --skill land-and-deploy-kakarottoooo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/Kakarottoooo/onegent/tree/main/.agents/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/Kakarottoooo/onegent --skill land-and-deploy-kakarottoooo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges pull requests, waits for CI to complete, deploys to production, and validates canary health to ensure safe releases without manual intervention.

Core Features & Use Cases

  • End-to-end release automation: merge PRs, monitor CI, trigger deployment, and verify health signals.
  • Safe rollback and canary-based validation to minimize production risk.
  • Suitable for teams using GitHub-based workflows who want reliable, hands-off releases.

Quick Start

Invoke the land-and-deploy skill on a ready PR to merge, trigger CI, and verify production health via canaries.

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 GitHub PR and verifying production health?▼

Automating GitHub PR merges and production health verification requires a workflow that merges the pull request, waits for CI completion, deploys, and validates canary checks. This ensures safe releases without manual intervention.

What is canary-based deployment validation in CI CD pipelines?▼

Canary-based deployment validation in CI CD pipelines is the process of monitoring production health signals after a release. It checks a subset of traffic to ensure safe deployments and enables rollback to minimize production risk.

Do I need GitHub CLI authentication to automate PR merges and deployments?▼

Yes, GitHub CLI authentication is required to automate PR merges and deployments. You also need a mergeable PR on the current branch and access to deployment health verification steps.

How do I wait for CI to complete after merging a pull request?▼

Waiting for CI to complete after merging a pull request is handled by monitoring the GitHub workflow gates. The automation tracks CI progress and proceeds to deploy only after checks pass successfully.

When should I use automated release workflows for GitHub deployments?▼

Automated release workflows for GitHub deployments are ideal for teams wanting reliable, hands-off releases. They suit typical GitHub workflow scenarios where a mergeable PR progresses through CI and deployment gates safely.

Can I rollback a production deployment if canary health checks fail?▼

Yes, rollback is supported if canary health checks fail. The workflow includes safe canary-based validation to detect unhealthy production signals, minimizing risk and ensuring reliable releases.

Related Skills

Explore More Software Engineering Skills→
anishs1207anishs1207
1

land-and-deploy

Merge a PR after CI passes and verify production health via canary checks.

Community
Advanced
mr-daedaliummr-daedalium
107

land-and-deploy

Merge PRs, trigger deployment, and verify canary health in CI/CD pipelines.

Community
Advanced
omerakbenomerakben
1

git-workflow-deployment

Automate Git branching, CI/CD gates, and Vercel production deployments.

Community
Intermediate
a29paula29paul
1

land-and-deploy

Merge approved PRs, wait for CI and deployment pipelines, and verify production canary checks.

Community
Advanced