land

Squash-merge a PR and clean up local and remote branches.

29|4|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/matsen/bipartite --skill land-matsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land
Source: https://github.com/matsen/bipartite/tree/main/skills/land
Command: npx skills add https://github.com/matsen/bipartite --skill land-matsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Landing a PR can be fiddly and error-prone if commits are scattered; this skill streamlines the process by squash-merging the PR branch, and cleaning up both local and remote branches, then returning you to main.

Core Features & Use Cases

  • Squash-merge the current branch's PR to the base
  • Clean up local and remote branches after landing
  • Return to the main branch for continued work
  • Use Case: when finishing a feature branch, quickly land the PR and keep the repo tidy

Quick Start

Invoke the landing command to squash-merge the current PR and clean up local and remote branches, then return to main.

Frequently Asked Questions about land

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

FAQPage Schema
How do I squash-merge a pull request and clean up branches automatically?

To squash-merge a pull request and clean up branches, you can automate the process by identifying the current PR, performing the squash merge, force-pushing, deleting local and remote feature branches, and returning to the base branch with a clean workspace.

What is the best way to tidy up local and remote git branches after landing a PR?

The best way to tidy up local and remote git branches after landing a PR is to automate the cleanup during the squash-merge process, ensuring both local and remote feature branches are deleted while returning you to the main branch.

How does a squash merge workflow keep my git repository clean?

A squash merge workflow keeps your git repository clean by combining scattered commits into a single commit on the base branch, then automatically deleting the merged feature branch locally and remotely to prevent branch clutter.

Can I automate returning to the main branch after completing a squash merge?

Yes, you can automate returning to the main branch after completing a squash merge. The workflow checks out the base branch and ensures a clean workspace immediately after the feature branch is deleted locally and remotely.

Do I need to force push when performing a squash merge for PR management?

Yes, you need to force push when performing a squash merge for PR management. Because the squash rewrite alters the commit history, pushing with force is required to update the remote base branch during the landing process.