land-and-deploy

Automate PR merging, CI waiting, production deployment, and canary health checks.

15|1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/howdeploy/NekoFree --skill land-and-deploy-howdeploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/howdeploy/NekoFree/tree/main/skills/land-and-deploy
Command: npx skills add https://github.com/howdeploy/NekoFree --skill land-and-deploy-howdeploy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Land and deploy workflow automation solves the end-to-end release process by orchestrating PR merging, CI waiting, production deployment, and health verifications. It ensures post-ship activities like creating the PR and canary health checks are handled consistently.

Core Features & Use Cases

  • Automated PR merge, CI gate waiting, and production deployment in a repeatable workflow.
  • Canary health validation and post-deploy PR updates to reflect production status.
  • Handles branching, routing, and project-level onboarding for release orchestration to reduce manual toil.

Quick Start

Tell the agent to execute land-and-deploy: merge the PR, wait for CI, deploy to production, perform canary checks, and create the PR after ship.

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, waiting for CI, and deploying to production?

Automating your release workflow involves orchestrating PR merges, waiting for CI gates, deploying to production, and validating health with canary checks. This process ensures consistent end-to-end releases by handling gating, deployment, and post-ship PR updates automatically.

What is a canary deployment and how does it validate production health?

A canary deployment validates production health by routing a portion of traffic to the new release and checking for errors. In this release workflow, canary checks are performed automatically after deploying to production to ensure stability before completing the process.

How do I handle post-release PR updates after a production deployment?

Post-release PR updates are handled automatically as part of the release workflow. After deploying to production and completing canary health validation, the workflow creates and updates PRs to reflect the current production status, reducing manual toil.

Can I configure CI gates and release orchestration steps for my project?

Yes, the release orchestration supports configurable steps for CI gates, canary deployments, and post-release updates. It handles branching, routing, and project-level onboarding to automate your specific release scenarios with robust context handling.

What is the best way to reduce manual toil in end-to-end release workflows?

The best way to reduce manual toil in release workflows is to automate the end-to-end process. By orchestrating PR merging, CI waiting, production deployment, and health verifications with configurable steps, you achieve repeatable and consistent releases.