pr-merge

Name: pr-merge
Availability: InStock
Author: proven-xyz

Merge GitHub pull requests with squash after CI checks pass.

2|1|Updated Mar 20, 2026

Search Tags:#automation #workflow #github #ci #pull-request #pr-merge

Ready to run

npx skills add https://github.com/proven-xyz/proven-app --skill pr-merge-proven-xyz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-merge
Source: https://github.com/proven-xyz/proven-app/tree/main/.agents/skills/pr-merge
Command: npx skills add https://github.com/proven-xyz/proven-app --skill pr-merge-proven-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge GitHub pull requests with strict CI validation. Never bypasses failed checks. Use when merging PRs or when user says /pr-merge.

Core Features & Use Cases

Merges GitHub PRs via gh pr merge --squash with automated checks
Requires GitHub CLI installed and authenticated; PR must exist for the branch
Stop hook: task claude:validate-skill -- --skill pr-merge
Critical Rule: NEVER bypass CI checks; if checks fail, do not merge

Quick Start

Use the pr-merge skill to merge a PR only after all checks pass or when the user explicitly requests /pr-merge.

Frequently Asked Questions about pr-merge

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

FAQPage Schema

How do I automatically merge a GitHub pull request only after CI checks pass?▼

Automating a GitHub pull request merge with strict CI validation requires enforcing checks before executing a squash merge. This process prevents bypassing failed validation and ensures code stability by using the GitHub CLI to merge only when all status checks succeed.

Can I merge a pull request via the command line without bypassing failed CI checks?▼

Merging a pull request via the command line without bypassing failed CI checks requires a strict validation mechanism. By using the GitHub CLI to enforce checks, the merge process halts if validation fails, ensuring that only successfully validated code is merged.

What do I need to set up before automating pull request merges with GitHub CLI?▼

Automating pull request merges requires the GitHub CLI installed and authenticated, an existing pull request for the target branch, and proper repository access. These prerequisites ensure the merge process can execute squash merges and validate CI checks successfully.

Why does my automated pull request merge fail when CI checks are not passing?▼

An automated pull request merge fails when CI checks are not passing because the process strictly enforces validation and prevents bypasses. If checks fail, the system intentionally halts the squash merge to ensure that unvalidated or broken code is never merged into the repository.

When should I use an automated CI-validated merge for my pull requests?▼

You should use an automated CI-validated merge when you need to safely merge pull requests across repositories and guarantee that no failing checks are bypassed. It is applicable whenever you are merging branches or explicitly request a validated squash merge.

Does the automated PR merge process use squash merging or standard merging?▼

The automated PR merge process uses squash merging to integrate pull requests. By executing a squash merge with the GitHub CLI, it combines all commits into one while strictly enforcing CI validation to prevent bypassing any failed checks before the merge completes.