pr-land

Enforce readiness checks and execute merges for pull requests.

Updated Aug 23, 2026

Search Tags:#automation #merge #branch #policy #pull-request #checks

Ready to run

npx skills add https://github.com/hack-ink/codexlab --skill pr-land

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-land
Source: https://github.com/hack-ink/codexlab/tree/main/.codex/skills/pr-land
Command: npx skills add https://github.com/hack-ink/codexlab --skill pr-land

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRs ready to land require coordinated checks, policy-driven merge decisions, and safe merge execution without collateral cleanup tasks.

Core Features & Use Cases

Enforces PR readiness checks and applies a delivery-history-aware merge policy.
Coordinates necessary branch sync decisions and performs merge execution when eligible.
Explicitly notes that it does not produce delivery/1, close trackers, or clean up worktrees.

Quick Start

Trigger the landing workflow by providing a ready PR URL and policy context, then let the skill perform the merge when gates pass.

Frequently Asked Questions about pr-land

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

FAQPage Schema

How do I automate pull request merges with policy checks?▼

To automate pull request merges with policy checks, provide a ready PR URL and policy context to trigger the landing workflow, which validates checks and executes the merge when readiness gates pass.

What is a delivery-history-aware merge policy?▼

A delivery-history-aware merge policy evaluates past delivery records to determine merge eligibility, ensuring a pull request only lands when it meets established historical delivery criteria and readiness checks.

How do I synchronize a base branch before executing a PR merge?▼

To synchronize a base branch before a PR merge, the landing workflow coordinates necessary branch sync decisions automatically, validating base freshness and routing through the proper flow before executing the merge.

Does automated PR merging handle worktree cleanup or delivery tracker closures?▼

No, automated PR merging via this workflow explicitly does not handle worktree cleanup, delivery tracker closures, or delivery task generation, focusing solely on policy checks and merge execution.

What is the best way to enforce readiness checks before landing a pull request?▼

The best way to enforce readiness checks before landing a pull request is using a policy-driven workflow that validates PR state, checks status, and base branch freshness before authorizing merge execution.