land

Resolve conflicts, wait for CI checks, and squash-merge pull requests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/johngrandson/orkestry --skill land-johngrandson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land
Source: https://github.com/johngrandson/orkestry/tree/main/.claude/skills/land
Command: npx skills add https://github.com/johngrandson/orkestry --skill land-johngrandson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the safe landing of a pull request by detecting and resolving merge conflicts, monitoring CI checks, and performing a squash-merge when all checks pass, reducing manual toil and preventing broken merges.

Core Features & Use Cases

  • Conflict detection and resolution guidance to ensure the PR can be landed without breaking the main branch.
  • CI status polling and gating to wait for checks to complete before merging, with timeouts and clear failure messaging.
  • Automated squash-merge and post-merge cleanup to keep branches tidy and history intact.
  • Use case: When multiple team members contribute to a PR or when a PR requires automated handling to meet organizational gating and compliance.

Quick Start

Run the land skill to monitor a pull request, resolve conflicts, wait for checks to pass, and squash-merge when green.

Frequently Asked Questions about land

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

FAQPage Schema
How do I automatically resolve merge conflicts and land a pull request?

To automatically resolve merge conflicts and land a pull request, this automation detects conflicts, provides resolution guidance, polls CI checks, and performs a squash merge when green. It reduces manual toil by safely handling the entire PR landing workflow.

What is the best way to automate squash merging a GitHub PR after CI checks pass?

The best way to automate squash merging a GitHub PR is to use an automated land skill that polls CI status, gates merging on passing checks, and executes a squash-merge. This prevents broken merges and keeps branch history intact.

Can I automate GitHub pull request merging for multiple team members contributing to the same PR?

Yes, you can automate GitHub pull request merging when multiple team members contribute. The automation handles organizational gating, compliance requirements, conflict detection, and CI status polling to safely land the PR.

How does CI status polling and gating work for automated pull request merges?

CI status polling and gating works by continuously monitoring check statuses with timeouts before merging. The automation waits for checks to complete, provides clear failure messaging if they fail, and only performs the merge when all checks pass.

Why does automated PR merging fail when CI checks time out or conflicts remain unresolved?

Automated PR merging fails when CI checks time out or conflicts remain unresolved to prevent broken merges into the main branch. The automation provides clear failure messaging to ensure the PR can only land when checks pass and conflicts are resolved.