merge-pr

Merge pull requests after verifying approvals, status checks, and branch protections.

1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/squirrel289/pax --skill merge-pr-squirrel289
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/squirrel289/pax/tree/main/skills/workflow/merge-pr
Command: npx skills add https://github.com/squirrel289/pax --skill merge-pr-squirrel289

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates merging pull requests after comprehensive verification to prevent unsafe merges.

Core Features & Use Cases

  • Pre-merge verification of readiness (approvals, status checks, and branch protection)
  • Deterministic, auditable merge execution in YOLO or collaborative mode
  • Post-merge cleanup and reporting for traceability

Quick Start

Provide pr-number and repository, then trigger the workflow to merge after all checks pass.

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 a pull request only after CI checks and approvals pass?

Automated pull request merging verifies required approvals, branch protections, and CI status checks before executing the merge. This prevents unsafe merges by ensuring all pre-merge conditions are satisfied deterministically.

What is the safest way to merge pull requests with required branch protections?

The safest way to merge pull requests with branch protections is to use automated pre-merge verification that validates required approvals and status checks before executing the merge. This ensures consistent, auditable workflows.

Can I trigger a git workflow to merge a PR automatically in YOLO mode?

Yes, you can trigger automated git workflow merging in YOLO mode for immediate execution, or use collaborative mode. Both modes validate branch protections and status checks before completing the pull request merge.

Does automated PR merging work with GitHub repositories that require CI status checks?

Yes, automated PR merging works directly with GitHub-style repositories by validating CI status checks and required approvals. It enforces branch protection rules before executing the merge to prevent unsafe code integration.

What happens if a pull request merge fails pre-merge verification?

If a pull request fails pre-merge verification, the automated merge is blocked to prevent unsafe merges. The system checks approvals, status checks, and branch protections, stopping execution if required conditions are unmet.

How do I clean up branches after an automated pull request merge?

After an automated pull request merge completes, post-merge cleanup removes the merged branch and generates reports for traceability. This ensures consistent repository hygiene across the team's auditable merge workflows.