merge-pr

Automates GitHub pull request merging with conflict and CI checks, supporting multiple merge strategies and dry-run mode.

1|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/YH-05/finance --skill merge-pr-yh-05
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/YH-05/finance/tree/main/.claude/skills/merge-pr
Command: npx skills add https://github.com/YH-05/finance --skill merge-pr-yh-05

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of merging GitHub Pull Requests, ensuring that conflicts are checked, CI passes, and the merge is performed safely and efficiently.

Core Features & Use Cases

  • Conflict Detection: Automatically checks for merge conflicts before attempting a merge.
  • CI Status Verification: Ensures all continuous integration checks have passed.
  • Multiple Merge Strategies: Supports standard merge, squash merge, and rebase merge.
  • Branch Management: Option to automatically delete the source branch after a successful merge.
  • Dry Run Mode: Allows for a simulation of the merge process without actual execution.

Quick Start

Use the merge-pr skill to squash merge pull request number 456 and delete the branch.

Frequently Asked Questions about merge-pr

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

FAQPage Schema
How do I safely merge a GitHub PR automatically without causing CI failures?

To safely merge a GitHub PR automatically, this Skill checks for merge conflicts and verifies that all continuous integration statuses have passed before executing the merge operation.

Can I automate squash merge and rebase strategies for pull requests using a script?

Yes, you can automate pull request merges using scripts that support multiple merge strategies, including standard merge, squash merge, and rebase merge, alongside automatic branch deletion options.

Do I need the gh CLI tool installed to automate pull request merging?

Yes, you need the gh CLI tool installed, as the automation scripts rely on it to interact with GitHub repositories, check CI status, and execute the pull request merge.

What is the best way to test a pull request merge before actually executing it?

The best way to test a pull request merge is by using a dry-run mode, which simulates the entire merge process and validates conflicts and CI status without performing actual execution.