skills.rest
zhaow-de
zhaow-deCOMMUNITY
Explore all skills by this author →
GitHub

merge-pr

Merge reviewed GitHub pull requests with a merge commit.

Updated Jul 6, 2026
Search Tags:#pull request#GitHub#merge#Code Review#Automation
One-click install
npx skills add https://github.com/zhaow-de/zcrypto-kraken --skill merge-pr-zhaow-de
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/zhaow-de/zcrypto-kraken/tree/main/.claude/skills/merge-pr
Command: npx skills add https://github.com/zhaow-de/zcrypto-kraken --skill merge-pr-zhaow-de

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of merging reviewed GitHub pull requests, ensuring that the local clone is cleaned up afterward.

Core Features & Use Cases

  • Automated Merge: Merges pull requests with a merge commit, avoiding squash or rebase.
  • Local Cleanup: Cleans up local branches after merging.
  • Gate Checks: Performs checks to ensure the pull request is ready to merge.

Quick Start

Use the merge-pr skill to merge PR #60 and clean up the local state.

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 reviewed GitHub pull requests?▼

Automate merging reviewed GitHub pull requests by using a script that merges with a merge commit and performs gate checks for base branch validation, conflict resolution, and review status before merging.

Can I merge a pull request with a merge commit instead of squashing?▼

Yes, merging a pull request with a merge commit is supported, explicitly avoiding squash or rebase methods to preserve the full commit history and perform local branch cleanup afterward.

What checks are needed before merging a GitHub pull request?▼

Before merging a GitHub pull request, checks include base branch validation, conflict resolution verification, and review status confirmation to ensure the pull request is ready to merge.

Do I need the GitHub CLI to merge pull requests automatically?▼

Yes, the GitHub CLI is required to access the GitHub API and execute git commands for validating pull request readiness and performing the automated merge commit.

How does local branch cleanup work after merging a pull request?▼

Local branch cleanup happens automatically after merging a pull request, removing the local branches associated with the merged pull request to keep the local clone clean.

What happens if a pull request has conflicts during automated merge?▼

If a pull request has conflicts, the automated merge process performs conflict resolution checks and halts the merge to prevent merging unresolved conflicts into the base branch.

Related Skills

Explore More Software Engineering Skills→
davpatel605-beepdavpatel605-beep

github-pr-workflow

Manage GitHub pull requests from branch creation through merge.

Community
Advanced
nsheapsnsheaps
3

update-branch

Synchronize feature branches with their PR base using git and gh.

Community
Advanced
chf3198chf3198

github-review-merge-admin

Validate GitHub pull request approvals, status checks, and merge readiness.

Community
Intermediate
ilonatommyilonatommy
3

commit-squashing

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

Community
Intermediate