skills.rest
CaltexBevo
CaltexBevoCOMMUNITY
Explore all skills by this author →
GitHub

land-and-deploy

Merge GitHub PRs, wait for CI, deploy to production, and run canary checks.

Updated Feb 5, 2026
Search Tags:#automation#github#release-management#ci-cd#canary#pr-merge#land-and-deploy
One-click install
npx skills add https://github.com/CaltexBevo/ihe-pulse --skill land-and-deploy-caltexbevo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/CaltexBevo/ihe-pulse/tree/main/.claude/skills/gstack.bak/land-and-deploy
Command: npx skills add https://github.com/CaltexBevo/ihe-pulse --skill land-and-deploy-caltexbevo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy workflow that merges PRs, waits for CI, deploys to production, and verifies production health via canary checks.

Core Features & Use Cases

  • End-to-end PR merge and deploy: merges PR, waits for CI, deploys, and runs canary checks.
  • Post-ship takeover: takes over after /ship creates the PR and ensures production readiness.
  • Use cases: teams using GitHub PR flow who want automated deployment and health validation before production release.

Quick Start

Trigger land-and-deploy on a ready PR to automatically merge, deploy, and verify production health with canary checks.

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 GitHub PR merge, CI checks, and production deployment in one workflow?▼

Automated land and deploy workflows merge your GitHub PR, wait for CI pipelines to pass, deploy to production, and run canary health checks to verify end-to-end production readiness.

What is a canary check in an automated CI/CD deployment pipeline?▼

Canary checks in CI/CD deployment verify production health immediately after a PR merge and deploy, ensuring the newly released application is stable and ready before completing the workflow.

Can I integrate automated deployment with my existing GitHub PR flow?▼

Yes, the workflow integrates with existing GitHub PR flows and can take over after PR creation to enforce the merge, CI, deploy, and canary verification sequence automatically.

What's the best way to ensure production readiness after merging a GitHub PR?▼

Enforce a sequential land and deploy process that merges the PR, waits for CI completion, deploys to production, and runs canary checks to validate production health and readiness.

Do I need to manually trigger deployment after CI passes on a merged PR?▼

No, the land and deploy workflow automates the entire sequence after PR approval, waiting for CI to pass and deploying to production without manual intervention for hands-off releases.

When should I not use an automated land and deploy workflow for releases?▼

Avoid automated land and deploy workflows if your GitHub PRs require manual deployment approvals, custom staging gates, or canary health checks outside the standard production pipeline.

Related Skills

Explore More Software Engineering Skills→
gigagiovagigagiova

github-pr-workflow

Orchestrate GitHub pull request lifecycles using gh CLI and REST API calls.

Community
Advanced
ShmurdocShmurdoc

land-and-deploy

Merge pull requests, monitor CI pipelines, and verify production canary health.

Community
Advanced
EthansuttorEthansuttor

agent-github-modes

Coordinate GitHub workflows, PRs, and issues across multiple repositories.

Community
Advanced
SeaLion-hubSeaLion-hub

land-and-deploy

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

Community
Advanced