skills.rest
badbsallyy
badbsallyyCOMMUNITY
Explore all skills by this author →
GitHub

merge-pr

Merge GitHub pull requests via squash and clean up worktrees.

Updated Feb 15, 2026
Search Tags:#automation#git#github#merge#pr#squash
One-click install
npx skills add https://github.com/badbsallyy/openclaw-source-code --skill merge-pr-badbsallyy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/badbsallyy/openclaw-source-code/tree/main/openclaw-sourcecode.zip/.agents/skills/merge-pr
Command: npx skills add https://github.com/badbsallyy/openclaw-source-code --skill merge-pr-badbsallyy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of merging prepared GitHub Pull Requests (PRs) using a squash strategy, ensuring a clean and efficient integration into the main branch.

Core Features & Use Cases

  • Squash Merging: Merges PRs by squashing all commits into a single commit on the target branch.
  • Automated Cleanup: Removes the feature branch after a successful merge.
  • Worktree Isolation: Performs all operations within a dedicated worktree to prevent interference with the main development environment.
  • Use Case: After a PR has been reviewed and approved, use this Skill to merge it into the main branch without manual intervention, automatically cleaning up the associated branch.

Quick Start

Use the merge-pr skill to merge pull request number 123.

Frequently Asked Questions about merge-pr

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

FAQPage Schema
How do I automate merging a GitHub pull request using squash?▼

Squash merging a GitHub pull request combines all commits into a single commit on the target branch. This approach keeps the project history linear and clean, automatically cleaning up the feature branch after the PR reaches the MERGED state.

How does automated PR cleanup work after a squash merge?▼

Automated PR cleanup removes the feature branch and cleans up dedicated worktrees after a successful squash merge. This prevents branch accumulation and isolates operations to avoid interfering with your main development environment.

What do I need to provide to squash merge a PR automatically?▼

You need to provide the specific pull request number or URL to initiate the automated squash merge. The process also validates PR checks and branch status before merging to ensure integration readiness.

Does automated squash merging validate GitHub PR checks before merging?▼

Yes, automated squash merging validates PR checks and branch status before executing the merge. It ensures the pull request is fully reviewed and approved, preventing integration of failing or incomplete code.

When should I not use squash merge for my pull requests?▼

You should not use squash merge when you need to preserve individual commit history or specific commit metadata on the target branch. Squash merging condenses all commits into one, losing granular commit details.

Related Skills

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

Dev10x:gh-context

Detect and resolve GitHub Pull Request context from URLs, numbers, or branches.

Official
Advanced
ajsai47ajsai47
11

land-and-deploy

Merge GitHub pull requests and verify production health after deployment.

Community
Advanced
julianobarbosajulianobarbosa
7

Git

Automate Git commit, branch, merge, and PR workflows with GitHub CLI and security checks.

Community
Advanced
ilonatommyilonatommy
3

commit-squashing

Consolidate multiple Git commits into a single commit using rebase, reset, or merge strategies.

Community
Intermediate