pr-merge

Validate CI/CD checks, reviews, conflicts, then merge GitHub PRs via squash, merge, or rebase.

25|2|Updated Oct 26, 2025
One-click install
npx skills add https://github.com/matteocervelli/llms --skill pr-merge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-merge
Source: https://github.com/matteocervelli/llms/tree/main/.claude/skills/pr-merge
Command: npx skills add https://github.com/matteocervelli/llms --skill pr-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates manual pre-merge checks and ensures that GitHub pull requests are merged only after passing all critical validations, preventing broken builds, maintaining code quality, and streamlining development workflows.

Core Features & Use Cases

  • Comprehensive Pre-Merge Validation: Automatically checks CI/CD status, verifies required code reviews, and identifies merge conflicts before any merge operation.
  • Flexible Merge Strategies: Supports squash, merge, and rebase methods, allowing you to choose the appropriate strategy based on project conventions and desired commit history.
  • GitHub MCP Integration: Leverages GitHub's native tools for seamless, secure, and compliant operations directly within your repository.
  • Use Case: A developer finishes a feature branch and asks, "Merge PR #123." This skill will verify all checks, reviews, and conflicts, then execute the merge using the appropriate strategy (e.g., squash merge), providing a clean, validated main branch.

Quick Start

Merge pull request #456 in the 'my-org/my-repo' repository using a squash merge, ensuring all checks pass.

Frequently Asked Questions about pr-merge

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

FAQPage Schema
How do I automate GitHub pull request merges with safety checks?

Automated PR merging validates CI/CD status, code review approvals, and merge conflicts before executing the merge. This Skill fetches PR details, assesses required checks, verifies approvals, detects conflicts, and merges using your project's preferred strategy—squash, merge, or rebase—ensuring only validated PRs reach your main branch.

What pre-merge validations does automated PR merging perform?

Pre-merge validation checks CI/CD pipeline status, confirms required code reviews are complete, identifies merge conflicts, and optionally reviews changed files. These checks run before any merge operation executes, preventing broken builds and maintaining code quality standards.

Can I choose different merge strategies when automating pull request merges?

Yes, automated PR merging supports squash, merge, and rebase strategies. You select the appropriate method based on your project conventions and desired commit history, allowing clean, validated merges tailored to your workflow preferences.

Does automated PR merging work with GitHub repositories across multiple projects?

Yes, this Skill applies to open PRs across multiple repositories within GitHub. It handles comprehensive validation and merging workflows consistently across your organization's projects using GitHub MCP integration for seamless, secure operations.

What happens if a pull request fails validation during automated merging?

If a PR fails any validation—incomplete reviews, failing CI/CD checks, or detected conflicts—the merge does not execute. The Skill reports validation failures, preventing broken code from reaching your main branch and allowing developers to address issues first.