land

Execute post-merge deployment runbooks to verify pipelines, migrations, and service health.

Updated Jul 3, 2026

Search Tags:#automation #ci/cd #deployment #migration #release engineering #canary

Ready to run

npx skills add https://github.com/ohyesgocool/feature-loop --skill land-ohyesgocool

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: land
Source: https://github.com/ohyesgocool/feature-loop/tree/main/skills/land
Command: npx skills add https://github.com/ohyesgocool/feature-loop --skill land-ohyesgocool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill bridges the gap between a merged pull request and a verified production release by automating the complex, error-prone sequence of pipelines, migrations, and health checks.

Core Features & Use Cases

Runbook-Driven Execution: Automatically drafts or follows a project-specific landing runbook to ensure consistent deployment procedures.
Safety-First Verification: Enforces strict verification of every step, including pipeline status, database migrations, and canary health checks, with clear separation between agent-executable and human-required tasks.
Use Case: After merging a feature, use this skill to safely deploy the code, run necessary migrations, and verify system health across multiple services without manual oversight.

Quick Start

Ask the agent to land the latest merged pull request by running the command land latest.

Frequently Asked Questions about land

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate post-merge deployments and verification across multiple services?▼

Automated post-merge deployments use project-specific runbooks to orchestrate pipelines, database migrations, and service health checks. This bridges the gap between a merged pull request and a verified production release without manual oversight.

What is runbook-driven release engineering for continuous integration?▼

Runbook-driven release engineering automatically drafts or follows project-specific landing procedures to ensure consistent deployment sequences. It enforces strict verification of pipeline status and system health with clear separation between agent-executable and human-required tasks.

How do I execute database migrations and canary monitoring during a deployment?▼

Database migrations and canary monitoring are executed by orchestrating the post-merge deployment lifecycle. The system enforces safety-first verification for every step, performing functional probes and maintaining strict safety guardrails for human-in-the-loop interventions.

Do I need CI/CD provider integration and infrastructure access for automated deployment verification?▼

Yes, automated deployment verification requires integration with CI/CD providers and infrastructure access. These integrations are necessary to execute project-specific runbooks, perform functional probes, and conduct canary monitoring across multiple repositories.

What is the best way to handle complex release sequences across multiple repositories?▼

Handling complex release sequences across multiple repositories is best managed by orchestrating the post-merge deployment lifecycle. This approach automates error-prone pipelines, migrations, and health checks while maintaining strict safety guardrails for human-in-the-loop interventions.

Why does my automated deployment require human-in-the-loop interventions?▼

Automated deployments require human-in-the-loop interventions because the system enforces strict safety guardrails. It maintains a clear separation between agent-executable and human-required tasks to verify pipeline status, migrations, and canary health safely.