skills.rest
RonHouben
RonHoubenCOMMUNITY
Explore all skills by this author →
GitHub

merge-pull-request

Merge approved GitHub pull requests via GitHub CLI after CI checks pass.

2|Updated Jan 30, 2026
Search Tags:#merge#workflow-automation#pull-request#github-cli#ci-passes#remote-cleanup
One-click install
npx skills add https://github.com/RonHouben/wavecraft --skill merge-pull-request
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-pull-request
Source: https://github.com/RonHouben/wavecraft/tree/main/.github/skills/merge-pull-request
Command: npx skills add https://github.com/RonHouben/wavecraft --skill merge-pull-request

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates merging of approved GitHub pull requests by validating CI status, enforcing review requirements, and preserving local branches, while cleaning up remote feature branches after merge.

Core Features & Use Cases

  • Verify PR status, approvals, and unresolved discussions before merging to ensure code quality.
  • Perform squash, rebase, or standard merge as configured, with a focus on clean history.
  • Clean up the remote feature branch after merge while always preserving the local branch for reference.
  • Sync the local repository post-merge by updating the main branch.
  • Provide clear error handling and guidance when CI or approvals are missing.

Quick Start

Run gh pr merge <PR_NUMBER> --squash and then delete the remote feature branch manually; the local branch is preserved.

Frequently Asked Questions about merge-pull-request

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

FAQPage Schema
How do I safely merge a GitHub pull request after CI checks pass?▼

Safely merge a GitHub pull request by automating the process to verify CI status, enforce review approvals, and check for unresolved discussions before merging. This ensures code quality and prevents merging unverified code.

Can I clean up the remote feature branch after merging while keeping the local branch?▼

Yes, you can clean up the remote feature branch after merging while always preserving the local branch for reference. This workflow automation synchronizes the local repository by updating the main branch post-merge.

Does the GitHub CLI support squash, rebase, and standard merge for pull requests?▼

The GitHub CLI supports squash, rebase, and standard merge for pull requests. You can configure the merge method to maintain a clean project history while ensuring the PR state is OPEN and fully approved.

Why does my pull request merge fail when CI or approvals are missing?▼

Your pull request merge fails when CI or approvals are missing because the workflow enforces PR state validation and review requirements. It provides clear error handling and guidance when prerequisites are unmet.

What is the best way to automate PR merging and synchronize the local repository?▼

Automate PR merging by using the GitHub CLI to validate CI status, perform the merge, delete the remote branch, and synchronize the local repository. This updates the main branch while preserving your local feature branch.

Related Skills

Explore More Software Engineering Skills→
bkelly-labbkelly-lab
50

approve-pr

Automate GitHub PR pre-flight checks, approval, and squash-merge with branch deletion.

Official
Intermediate
Soul-Brews-StudioSoul-Brews-Studio
116

merged

Switch to main, pull latest changes, and delete merged branches.

Official
Basic
ManfronEnricoManfronEnrico

workspace-enforce

Block merges when high-severity workspace violations lack waivers.

Community
Advanced
nashgaonashgao
3

Merge Pull Request Command

Merge pull requests into a target branch with validation and quality gates.

Community
Advanced