land-pr

To merge a pull request and delete the branch using the GitHub CLI, this Skill performs the merge using a squash or rebase strategy, deletes the remote branch, and switches to the base branch. It automates the entire cleanup process to prevent orphaned branches.

To check for dependent pull requests before merging, this Skill detects chained or dependent PRs targeting your current branch and warns you. This prevents accidentally closing dependent work during the merge and branch cleanup process.

To keep your local git repository tidy after closing a PR, this Skill switches to the base branch, fetches and pulls updates, and prunes stale remote-tracking references. This ensures your main branch is up to date and removes orphaned branches.

Yes, you can choose between squash and rebase strategies when landing a PR. The default strategy is squash merge, but you can request a rebase merge instead to complete the pull request and clean up the remote branch.

If errors occur during a GitHub CLI pull request merge, the Skill aborts the operation. This safety mechanism ensures your repository remains in a consistent state if the merge, branch deletion, or remote-tracking ref pruning fails.

Yes, you need both gh and git installed to automate pull request branch cleanup. The Skill requires the GitHub CLI and git to perform the merge, delete remote branches, fetch base branch updates, and prune stale references.