land

Merge approved GitHub pull requests and complete related coordinator tasks.

4|Updated Feb 1, 2026

Search Tags:#automation #workflow #github #merge #coordinator #ci #pull-request

Ready to run

npx skills add https://github.com/mkalkere/agent-coordinator --skill land-mkalkere

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: land
Source: https://github.com/mkalkere/agent-coordinator/tree/main/.os/skills/lifecycle/land
Command: npx skills add https://github.com/mkalkere/agent-coordinator --skill land-mkalkere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge an approved pull request and automatically complete the related coordinator task, reducing manual handoffs and timeline gaps.

Core Features & Use Cases

Verify approvals and CI status before merging
Perform squash merge and delete the feature branch
Publish a task_completed bus event and update the coordinator when task_id is provided
Works in standalone mode when AC_COORDINATOR_URL is not set

Quick Start

To land a PR, supply the PR number and (optionally) the task_id; the skill will verify approval and CI, squash-merge the PR, delete the branch, and publish a task_completed event.

Frequently Asked Questions about land

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

FAQPage Schema

How do I automatically merge an approved GitHub pull request?▼

Automatically merge approved GitHub pull requests by supplying the PR number and optional task ID. The workflow verifies approval and CI status, performs a squash merge, deletes the feature branch, and publishes a task completed bus event.

What are the prerequisites for automating a GitHub PR merge with a coordinator?▼

Automating a GitHub PR merge requires a pull request number and optionally a task ID. The environment must use the gh pr merge command, and a coordinator URL must be set if you want to automatically update the coordinator task.

How does the merge workflow handle CI checks and branch deletion?▼

The merge workflow enforces pre-merge checks for CI status and approvals before proceeding. After performing a squash merge, it automatically deletes the feature branch to keep the repository clean and reduce manual handoffs.

Can I use the GitHub merge automation in standalone mode without a coordinator?▼

Yes, the GitHub merge automation works in standalone mode. When the AC_COORDINATOR_URL environment variable is not set, the workflow performs the squash merge and branch deletion without attempting to publish task completed bus events.

Why does my pull request merge automation fail before completion?▼

Pull request merge automation fails if pre-merge checks are not satisfied. The workflow explicitly enforces both approval and CI status checks before executing the squash merge, preventing incomplete or unreviewed changes from landing.