pr-merge

Generate a squash-merge commit message from PR metadata and reviews.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writes a clean, deterministic squash-merge commit message for an approved PR, reducing manual editing and human error.

Core Features & Use Cases

  • Generates a concise squash-merge commit message from PR metadata, reviews, and history to ensure a consistent history.
  • Integrates with GitHub Actions to finalize merges automatically for approved PRs.

Quick Start

Provide the pull request number or URL to generate the squash-merge commit message.

Frequently Asked Questions about pr-merge

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

FAQPage Schema
How do I automatically generate squash-merge commit messages for approved pull requests?▼

You can automatically generate a clean squash-merge commit message by running a GitHub Actions workflow on the PR branch. The process extracts PR metadata, review comments, and commit history to craft a consistent, policy-compliant message without manual editing.

What is the best way to ensure consistent PR commit messages in GitHub Actions?▼

The best way to ensure consistent PR commit messages is to automate the squash-merge message generation inside GitHub Actions. By using PR metadata and commit history, the workflow produces a deterministic and policy-compliant commit message for every approved pull request.

Does GitHub Actions support writing commit messages from PR review comments?▼

Yes, GitHub Actions supports writing commit messages from PR review comments. A workflow operating inside the GitHub Actions VM on the PR branch can aggregate metadata, reviews, and history to finalize a clean, deterministic squash-merge commit message.

Can I use pull request metadata to create a policy-compliant squash-merge message?▼

Yes, you can use pull request metadata to create a policy-compliant squash-merge message. By operating directly on the PR branch within a GitHub Actions VM, the process leverages PR metadata and commit history to craft a consistent, deterministic final message.

Why do my squash-merge commit messages lack consistency across approved PRs?▼

Squash-merge commit messages lack consistency due to manual editing and human error. Automating the message generation with GitHub Actions using PR metadata, review comments, and commit history ensures a deterministic, policy-compliant final message for every approved PR.