pr-merge

Read, summarize, and merge GitHub pull requests with conventional commit subjects.

Updated Mar 23, 2026

Search Tags:#automation #github #merge #comment #pull-request #pr-review #conventional-commit

Ready to run

npx skills add https://github.com/mia-cx/.agents --skill pr-merge-mia-cx

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges pull requests with style, providing a flavourful summary as a PR comment and then executing a clean conventional-commit merge to keep the git log readable.

Core Features & Use Cases

Read PR context (title, body, headRefName, baseRefName, commits, files, reviews, comments, labels, milestone) to understand changes.
Post a flavourful summary as a PR comment on GitHub so the timeline stays informative.
Merge using a conventional commit subject, enforcing consistency and traceability.
Use this workflow when a PR is ready to merge and you want context-rich history without noise.

Quick Start

Provide the PR number or URL and instruct the system to post a flavourful summary as a PR comment, then perform the merge with a conventional commit subject.

Frequently Asked Questions about pr-merge

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

FAQPage Schema

How do I automate GitHub pull request merges with conventional commit messages?▼

You can automate GitHub pull request merges by providing a PR number or URL to extract context, post a summary comment, and execute a conventional commit merge for a readable git log.

Can I post a summary comment on a GitHub pull request before merging it?▼

Yes, you can post a flavourful summary as a PR comment on GitHub before merging, ensuring the timeline stays informative while enforcing conventional commit traceability.

How does automated PR merging verify readiness checks before executing the merge?▼

Automated PR merging verifies readiness checks by extracting PR context like reviews, commits, labels, and milestone data to ensure a safe, auditable merge performs only when the pull request is ready.

Do I need to provide a pull request URL to use the automated merge workflow?▼

You do not strictly need to provide a pull request URL; you can supply the PR number instead. The workflow accepts typical user-provided numbers or URLs across features, fixes, and chore merges.

What is the best way to keep my git log readable when merging GitHub pull requests?▼

The best way to keep your git log readable when merging GitHub pull requests is to enforce consistency by generating a conventional commit subject during the automated merge process.