land

Merge pull requests with conflict resolution, CI validation, and squash-merging.

Updated May 16, 2026
One-click install
npx skills add https://github.com/LuminairPrime/skill-tree-chopper --skill land-luminairprime
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land
Source: https://github.com/LuminairPrime/skill-tree-chopper/tree/main/vendors/s-hiraokuvscode-sidebar-terminal/.codex/skills/land
Command: npx skills add https://github.com/LuminairPrime/skill-tree-chopper --skill land-luminairprime

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) components.

What problem does it solve?

Manages the entire PR landing process, including conflict resolution, checking, and squash-merging, ensuring a smooth integration of contributions.

Core Features & Use Cases

  • Conflict Detection and Resolution: Monitors for merge conflicts and uses resolution skills to address them.
  • Continuous Integration Checks: Keeps CI green and fixes failures, then re-runs checks.
  • Squash-Merging: Automates the squash-merge of a PR once checks are successful.
  • Use Case: When a developer needs to ensure a Pull Request is landed with minimal disruption and is fully compliant with project standards.

Quick Start

Execute the 'land' skill to initiate the landing process for a specific Pull Request.

Frequently Asked Questions about land

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

FAQPage Schema
How do I automate Pull Request landing with squash merging and conflict resolution?

Automating Pull Request landing involves using a skill that detects merge conflicts, applies resolution strategies, validates Continuous Integration checks, and performs a squash-merge. This ensures smooth integration of code contributions with minimal manual intervention.

What is the best way to keep CI green when merging a GitHub Pull Request?

The best way to keep CI green during a Pull Request merge is to automate the landing process with a tool that monitors Continuous Integration checks. If failures occur, the tool fixes them and re-runs the checks before completing the squash-merge.

Do I need Git and GitHub CLI to automate squash-merging a PR?

Yes, you need Git and GitHub CLI installed to automate squash-merging a PR. These dependencies provide the necessary command-line interfaces to interact with repositories, resolve conflicts, validate CI, and execute the final merge.

How does conflict detection work during automated code merging?

Conflict detection during automated code merging works by monitoring the repository for merge conflicts as the PR is integrated. When conflicts are found, resolution skills are automatically applied to address the mismatches before proceeding to CI validation.

Can I streamline code contributions by automating PR checks and squash-merging?

Yes, you can streamline code contributions by automating the entire PR landing workflow. This process handles conflict resolution, enforces CI compliance by fixing failures, and executes a squash-merge once all checks pass successfully.

Why does automated PR landing fail when Continuous Integration checks are red?

Automated PR landing pauses when Continuous Integration checks fail because the workflow is designed to keep CI green. The automation attempts to fix the failures and re-run the checks rather than proceeding with a broken merge.