skills.rest
smallorbit
smallorbitCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

merge-pr

Squash-merge the open PR for the current branch and delete the remote branch.

Updated Apr 17, 2026
Search Tags:#automation#git#github#labels#pull-request#squash-merge#merge-pr
One-click install
npx skills add https://github.com/smallorbit/smallorbit-plugins --skill merge-pr-smallorbit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/smallorbit/smallorbit-plugins/tree/main/plugins/flowkit/skills/merge-pr
Command: npx skills add https://github.com/smallorbit/smallorbit-plugins --skill merge-pr-smallorbit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squash-merge the open PR for the current branch, delete the remote branch, and apply the merged-to-develop label to any issues referenced in the PR body.

Core Features & Use Cases

  • Squash-merge the open PR for the current branch to produce a clean history.
  • Delete the remote branch after merging to keep the repository tidy.
  • Label issues referenced in the PR body with merged-to-develop, skipping any on-hold items.
  • Works with GitHub CLI and standard PR workflows to streamline release processes.

Quick Start

Trigger the merge-pr skill with /merge-pr to squash-merge the open PR on the current branch and label referenced issues.

Frequently Asked Questions about merge-pr

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

FAQPage Schema
How do I squash-merge a GitHub pull request and delete the remote branch?▼

Squash-merging a GitHub pull request and deleting the remote branch is automated by scanning the current branch for an open PR, then running gh pr merge --squash --delete-branch to produce a clean history and tidy references.

How do I automatically label issues when a pull request is merged?▼

To automatically label issues when a pull request is merged, the PR body is scanned for references to closed issues, applying the merged-to-develop label while skipping any issues marked with on-hold labels.

Do I need the GitHub CLI to automate squash-merging pull requests?▼

Yes, automating squash-merging pull requests requires the GitHub CLI, as the process detects the PR number using gh pr list and gh pr view, and executes the merge via gh pr merge --squash.

Can I use this to squash-merge a pull request into the main branch?▼

No, you cannot use this to squash-merge a pull request into the main branch, because the automation explicitly ensures it never targets main, focusing solely on standard PR workflows for develop branches.

What is the best way to streamline a GitHub release process with squash-merge?▼

The best way to streamline a GitHub release process with squash-merge is to automate the entire workflow: squash the open PR, delete the remote branch, and update issue labels in a single action.

Related Skills

Explore More Software Engineering Skills→
nodatallnodatall
2

cleanup-merged-branches

Delete merged Git branches locally and remotely with safety checks.

Community
Intermediate
mixomatmixomat

clean-gone-branches

Delete local git branches marked [gone] while skipping worktree branches.

Community
Intermediate
levkisslevkiss

github

Manage GitHub repositories via GitHub CLI for commits, branches, pull requests, issues, releases, and Pages deployment.

Community
Advanced
tkerseytkersey
66

join

Automate GitHub PR management with CI gates and squash-merge via gh CLI.

Community
Advanced