land

Merge approved pull requests after resolving conflicts and passing CI checks.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/zhaozengqing4364-bit/sales-training-qoder --skill land-zhaozengqing4364-bit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land
Source: https://github.com/zhaozengqing4364-bit/sales-training-qoder/tree/main/.codex/skills/land
Command: npx skills add https://github.com/zhaozengqing4364-bit/sales-training-qoder --skill land-zhaozengqing4364-bit

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies and automates the process of merging pull requests by managing conflicts, review feedback, and checks, reducing manual effort and errors.

Core Features & Use Cases

  • Conflict Resolution: Detects merge conflicts and facilitates conflict fixing.
  • Review Management: Collects and interprets review comments and approval status.
  • Checks Monitoring: Watches and verifies CI/CD checks to ensure code quality.
  • Use Case: Developers can use this Skill to automatically oversee a pull request’s lifecycle, ensuring all review and validation steps are completed before merging.

Quick Start

Use the land skill to automatically review and merge an approved pull request after resolving conflicts and passing checks.

Frequently Asked Questions about land

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

FAQPage Schema
How do I automate merging approved GitHub pull requests?

Automate merging approved GitHub pull requests by using scripts that collect review feedback, verify continuous integration checks, and execute the merge. This reduces manual effort and prevents integration errors.

How does automated conflict resolution work for GitHub pull requests?

Automated conflict resolution for GitHub pull requests works by detecting merge conflicts and applying scripts to facilitate conflict fixing. This ensures safe and efficient code integration before merging.

Do I need GitHub CLI to automate pull request merging?

Yes, you need GitHub CLI and API access to automate pull request merging. These dependencies are required to manage conflict resolution, review status, and continuous integration checks.

Can I monitor continuous integration checks before merging a pull request?

Yes, you can monitor continuous integration checks before merging a pull request. The process watches and verifies CI/CD checks to ensure code quality and validation steps are completed successfully.

What is the best way to manage code review status and merge conflicts?

The best way to manage code review status and merge conflicts is to automate the pull request lifecycle. This involves interpreting approval status, resolving conflicts, and validating continuous integration checks before merging.

What happens if continuous integration checks fail during pull request merging?

If continuous integration checks fail during pull request merging, the automated process halts the integration. It watches and verifies checks to ensure all validation steps pass before allowing the merge.