github-pr-merge

Merge GitHub Pull Requests after validating pre-merge checks and cleanup.

9|2|Updated Mar 12, 2026

Search Tags:#github #lint #code-review #pull-request #tests #ci-checks #merge-pr

Ready to run

npx skills add https://github.com/hongmaple0820/agent-academy --skill github-pr-merge-hongmaple0820

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-pr-merge
Source: https://github.com/hongmaple0820/agent-academy/tree/main/skills/development/github-pr-merge
Command: npx skills add https://github.com/hongmaple0820/agent-academy --skill github-pr-merge-hongmaple0820

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically merge GitHub Pull Requests after validating the pre-merge checklist and handling post-merge cleanup, reducing manual overhead and preventing unverified changes from entering protected branches.

Core Features & Use Cases

Pre-merge validation: runs tests, lint, CI checks, and reviews to ensure PR readiness.
Safe merge execution: performs the merge with a concise, informative message and deletes the remote branch when configured.
Post-merge cleanup: updates local state and performs routine housekeeping after a merge.
Use case: teams that require strict gatekeeping for code changes and consistent post-merge processes.

Quick Start

Automatically merge a PR that has passed all checks and meets the pre-merge criteria.

Frequently Asked Questions about github-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 after CI checks pass?▼

Automatically merging a GitHub pull request requires validating a pre-merge checklist including tests, lint, CI checks, and reviews before executing the merge with a concise message and handling post-merge cleanup.

Can I enforce code review and test validation before merging a pull request?▼

Yes, enforcing code review and test validation before merging a pull request is achieved by applying pre-merge checks that ensure all CI, lint, and review criteria are met before execution.

What is the best way to automate pull request merges to prevent unverified changes in protected branches?▼

Automating pull request merges to prevent unverified changes in protected branches involves running pre-merge validations, confirming with the user, executing the merge, and performing routine post-merge housekeeping.

Does the automated PR merge process include deleting the remote branch?▼

Yes, the automated PR merge process includes deleting the remote branch when configured, alongside updating local state and performing routine post-merge housekeeping to maintain repository hygiene.

How do I handle post-merge cleanup after a GitHub pull request is merged?▼

Handling post-merge cleanup after a GitHub pull request is merged involves updating local state, deleting remote branches when configured, and performing routine housekeeping to finalize the workflow.

What pre-merge checks are required before automating a GitHub PR merge?▼

Pre-merge checks required before automating a GitHub PR merge include running tests, lint, CI checks, and reviews to ensure strict gatekeeping for code changes across standard PR workflows.