github-pr-merge

Merge GitHub Pull Requests after pre-merge checks and reviewer replies pass.

69|6|Updated Dec 21, 2025

Search Tags:#automation #workflow #github #validation #merge #pr #checks

Ready to run

npx skills add https://github.com/fvadicamo/dev-agent-skills --skill github-pr-merge

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges GitHub Pull Requests only after all pre-merge checks pass, ensuring reviews, tests, and CI results are validated before completion.

Core Features & Use Cases

Automates pre-merge validations by verifying tests, lint, and CI status.
Enforces reviewer replies and ensures no unreplied comments remain before merging.
Performs a safe merge using the preferred strategy, then cleans up the feature branch post-merge.

Quick Start

Tell the assistant to merge the current PR after all checks are green and all comments are addressed.

Frequently Asked Questions about github-pr-merge

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

FAQPage Schema

How do I automate GitHub PR merges only after CI checks pass?▼

To automate GitHub PR merges safely, this Skill enforces pre-merge validations by verifying tests, lint, and CI status before executing the merge, ensuring your PR is only merged when all checks are green.

Can I prevent merging a GitHub PR if reviewer comments are unresolved?▼

Yes, you can prevent merging a GitHub PR with unresolved comments. This Skill enforces reviewer readiness by verifying that no unreplied comments remain before proceeding with the merge.

What is the best way to safely merge a GitHub PR and delete the feature branch?▼

The best way to safely merge a GitHub PR and delete the feature branch is using this Skill, which performs a safe merge using the preferred strategy and then handles post-merge cleanup by deleting the feature branch.

Does this automated PR merge process require manual user confirmation?▼

Yes, the automated PR merge process requires manual user confirmation. This Skill includes user confirmation as a pre-merge step to ensure you have final approval before the checks are validated and the merge is executed.

Why does my GitHub PR merge fail when checks are still running?▼

Your GitHub PR merge fails when checks are running because this Skill strictly enforces pre-merge checks, preventing the merge process if CI results are incomplete or checks fail to ensure safe merging.

Can I use gh pr merge with --merge in an automated workflow?▼

Yes, you can use gh pr merge with --merge in an automated workflow. This Skill satisfies that functional requirement by using the command to complete the merge and subsequently cleaning up the feature branch.