skills.rest
tiancaiamao
tiancaiamaoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

land

Merge approved GitHub pull requests after CI checks pass and update task state.

5|Updated Feb 8, 2026
Search Tags:#pull request#github#merge#rebase#squash merge#ci checks#task state
One-click install
npx skills add https://github.com/tiancaiamao/ai --skill land-tiancaiamao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land
Source: https://github.com/tiancaiamao/ai/tree/main/skills/land
Command: npx skills add https://github.com/tiancaiamao/ai --skill land-tiancaiamao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, git, curl.

What problem does it solve?

This Skill automates the safe landing of an approved pull request, reducing manual merge work while guarding against broken checks, merge conflicts, and task-state drift.

Core Features & Use Cases

  • Approval gating: Verifies that the PR is open and approved before merging.
  • Conflict recovery: Rebases conflicting branches onto main and retries when possible.
  • CI awareness: Waits for checks to finish, blocks on failures, and reports status back to the PR and task system.
  • Operational cleanup: Merges with squash, deletes the branch, and optionally sends Slack notifications.
  • Use case: Use this Skill when a task is ready to move from human review to a completed merge with minimal manual intervention.

Quick Start

Use the land skill to merge the approved pull request for this task and update its status after CI passes.

Frequently Asked Questions about land

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

FAQPage Schema
How do I merge an approved GitHub pull request only after CI checks pass?▼

Merging an approved GitHub pull request safely requires polling CI checks to completion, blocking on failures, verifying approval status, and performing a squash merge to update the task state.

What is the best way to handle merge conflicts when landing a pull request onto main?▼

Handling merge conflicts during a pull request landing involves rebasing the conflicting branch onto main and retrying the merge operation when possible to ensure successful integration.

Do I need GitHub CLI authentication to automate squash merges and branch cleanup?▼

GitHub CLI authentication is required to automate squash merges, verify mergeability, delete branches, and update task states within GitHub-based workflows.

Can I automatically send Slack notifications after a CI-gated pull request merge?▼

You can automatically send Slack notifications after a CI-gated pull request merge by including an operational cleanup step that triggers alerts once the branch is deleted and the task state is updated.

Why does my pull request merge fail when CI checks are still running?▼

A pull request merge fails when CI checks are still running because CI-aware merging requires waiting for checks to finish, blocking the operation on failures to prevent broken builds.

How to update task state automatically after a release landing merge?▼

To update task state automatically after a release landing merge, configure the merge process to integrate with your task system and report CI status and merge completion back to the associated task.

Related Skills

Explore More Software Engineering Skills→
Dev10x-GuruDev10x-Guru
7

Dev10x:gh-pr-merge

Validate GitHub pull requests and merge them after pre-merge checks.

Official
Advanced
haleyrchaleyrc
2

feature-merge

Squash merge feature branch commits into main with a Conventional Commit message.

Community
Intermediate
lygavlygav

coding-triage

Diagnose coding team failures and select recovery actions via decision trees.

Community
Advanced
alexandersumeralexandersumer
1

clear-merge-blockers

Identify and resolve merge blockers in code repositories with CI/CD integration.

Community
Advanced