land

Name: land
Availability: InStock
Author: ReinaMacCredy

Automates Pull Request landing with conflict resolution, CI checks, and squash-merge via GitHub CLI.

Updated Mar 13, 2026

Search Tags:#automation #git #ci/cd #code review #pull request #github actions

Ready to run

npx skills add https://github.com/ReinaMacCredy/Maestro-CLI --skill land-reinamaccredy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: land
Source: https://github.com/ReinaMacCredy/Maestro-CLI/tree/main/.codex/skills/maestro%3Asymphony-setup/reference/codex-skills/land
Command: npx skills add https://github.com/ReinaMacCredy/Maestro-CLI --skill land-reinamaccredy

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of merging a Pull Request (PR) into the main branch, ensuring code quality and stability by handling conflicts, monitoring checks, and addressing feedback.

Core Features & Use Cases

Conflict Resolution: Automatically detects and resolves merge conflicts with the main branch.
CI/CD Monitoring: Watches Continuous Integration (CI) checks and ensures they pass before merging.
Review Feedback Handling: Manages and incorporates feedback from human and AI reviewers.
Automated Merging: Performs a squash-merge once all conditions are met.
Use Case: When you've finished coding a new feature, you can hand it off to the 'land' Skill to shepherd it through the final stages of merging, freeing you to start on the next task.

Quick Start

Use the land skill to automatically merge the current pull request after all checks pass.

Frequently Asked Questions about land

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

FAQPage Schema

How do I automate merging a pull request only after CI checks pass?▼

Automating a pull request merge after CI checks pass involves monitoring continuous integration statuses and performing a squash-merge once all conditions are met. This Skill handles that by tracking CI/CD checks, resolving conflicts, and managing review feedback automatically.

Do I need GitHub CLI installed to automate pull request merges?▼

Yes, you need GitHub CLI installed to automate pull request merges. This Skill requires authenticated GitHub CLI access to monitor checks, manage review feedback, and execute the final squash-merge into the main branch.

How can I handle merge conflicts automatically when landing code?▼

Handling merge conflicts automatically when landing code requires a tool that detects and resolves issues with the main branch. This Skill automates conflict resolution during the pull request landing process before attempting a squash-merge.

Can a pull request automation tool process feedback from AI reviewers?▼

Yes, this pull request automation tool processes feedback from AI reviewers. It manages and incorporates review comments from both human reviewers and AI-generated sources before merging the code into the main branch.

What is the best way to manage code review feedback before a squash-merge?▼

The best way to manage code review feedback before a squash-merge is to use an automated tool that monitors comments and resolves conflicts. This Skill handles both human and AI-generated review feedback, ensuring all conditions are met before merging.

Why does my automated PR merge stall when CI checks fail?▼

An automated PR merge stalls when CI checks fail because the tool is designed to watch continuous integration statuses and ensure they pass before proceeding. This prevents broken code from being squash-merged into the main branch.