land

Merges a GitHub pull request via squash and removes the feature branch.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/duanegoodner/agentrelay --skill land-duanegoodner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land
Source: https://github.com/duanegoodner/agentrelay/tree/main/.claude/skills/land
Command: npx skills add https://github.com/duanegoodner/agentrelay --skill land-duanegoodner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end process of merging a GitHub PR and tidying up the feature branch, reducing manual steps and keeping main history clean.

Core Features & Use Cases

  • Automated squash merge of a PR to main to produce a single, clean commit.
  • Automatic cleanup of the feature branch both locally and on the remote after merging.
  • Works with common PR workflows and can be integrated into CI/CD pipelines for consistent outcomes.

Quick Start

Invoke the land skill with a PR number or let it infer the active PR to perform a squash merge and clean up the feature branch.

Frequently Asked Questions about land

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

FAQPage Schema
How do I automate a git squash merge and delete the feature branch afterwards?

To automate a git squash merge and branch cleanup, you can use a workflow tool that identifies a pull request, squashes commits into main, and deletes the branch locally and remotely.

What is the best way to keep main history clean when merging pull requests?

The best way to keep main history clean during pull request merges is to perform a squash merge, which collapses all feature commits into a single commit on the main branch.

How does a pull request cleanup workflow handle local and remote branches?

A pull request cleanup workflow handles local and remote branches by automatically deleting the feature branch from your local git repository and the remote GitHub repository after merging.

Can I integrate automated git branch deletion into a CI/CD pipeline?

Yes, you can integrate automated git branch deletion into CI/CD pipelines to ensure consistent squash merges and immediate feature branch cleanup across standard software development workflows.

Do I need to provide a PR number to automate a GitHub pull request merge?

No, you do not need to explicitly provide a PR number to automate a GitHub pull request merge; the workflow can infer the active PR automatically or accept a PR number if specified.

Why does my feature branch remain after a pull request is merged into main?

Your feature branch remains after a merge because standard git workflows do not automatically delete branches; an automated cleanup process is required to remove it locally and remotely after the squash merge.