merge-pr

Automate final GitHub pull request verification and merge decisions with configurable gates.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/rnwolfe/engram --skill merge-pr-rnwolfe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/rnwolfe/engram/tree/main/.claude/skills/merge-pr
Command: npx skills add https://github.com/rnwolfe/engram --skill merge-pr-rnwolfe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the final verification and merging of pull requests, preventing risky merges by enforcing gates and human review when required.

Core Features & Use Cases

  • Final pre-merge checks: verifies PR status, reviews, and CI before merging
  • Configurable gating: honors human_merge_required and auto_merge_after_review settings
  • Standalone operation: can run independently after human review or as part of /forge-loop

Quick Start

Provide the PR number to merge-pr to perform final checks and merge.

Frequently Asked Questions about merge-pr

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

FAQPage Schema
How do I automate safe pull request merges on GitHub after CI passes?

To automate safe pull request merges, this skill verifies PR status, CI results, and human reviews before merging. It enforces configurable gating like auto_merge_after_review to prevent risky merges on GitHub projects.

Can I require human review before auto-merging a GitHub pull request?

Yes, you can require human review before auto-merging by setting the human_merge_required gate. The skill honors this configuration to ensure final pre-merge checks include mandatory human approval.

What is config-driven gatekeeping for GitHub pull requests?

Config-driven gatekeeping for GitHub pull requests is enforcing merge policies based on configurable settings like required human reviews and CI status. This mechanism prevents risky merges by verifying all gates pass.

How do I check for blocked PRs before attempting a merge?

To check for blocked PRs, provide the PR number to the skill. It performs final pre-merge verification and generates reporting for blocked PRs when CI results, reviews, or status checks fail.

Does this PR merge automation work independently of CI/CD pipeline tools?

Yes, this PR merge automation works independently by running standalone after human review or as part of a forge-loop. It evaluates existing CI results and gate configurations without needing direct CI/CD pipeline integration.