pr-commit-message

Write evidence-backed PR merge and squash commit messages from GitHub pull request data.

5.6k|645|Updated Feb 22, 2016
One-click install
npx skills add https://github.com/mono/SkiaSharp --skill pr-commit-message
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-commit-message
Source: https://github.com/mono/SkiaSharp/tree/main/.agents/skills/pr-commit-message
Command: npx skills add https://github.com/mono/SkiaSharp --skill pr-commit-message

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge and squash commit messages often become vague one-liners that lose the why behind a change, forcing future maintainers to reopen the PR to understand root causes, design decisions, and compatibility constraints. This Skill inspects the PR, linked issues, reviews, and diffs to produce a commit message that stands alone in git history.

Core Features & Use Cases

  • Evidence-gathering workflow: Uses GitHub CLI commands to inspect PR bodies, commits, reviews, inline comments, linked issues, and diffs before drafting.
  • Topic-based structuring: Classifies changes into material topics, explicit decisions, and mechanical derivatives, then formats multi-topic messages with named sections matching repository conventions.
  • Claim-proof verification: Checks references, quantifiers, before/after claims, and causal rationale against actual sources, and builds source-backed Co-authored-by attribution trailers.
  • Use Case: A maintainer merging a SkiaSharp PR that fixes a Windows startup crash asks for a merge commit message and receives a wrapped, sectioned message covering the symptom, root cause, delay-load fix, verification evidence, and attribution trailers.

Quick Start

Ask the assistant to create a merge commit message for a specific pull request number in your repository.

Frequently Asked Questions about pr-commit-message

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

FAQPage Schema
How do I write a good merge commit message for a pull request?

Inspect the PR title, body, commits, reviews, and full diff, then draft a message covering symptom, root cause, chosen fix, and evidence. This Skill automates that workflow using GitHub CLI queries and structures multi-topic changes into named sections.

How to generate a squash commit message from PR changes?

Gather the PR's linked issues, substantive diff hunks, and review feedback, then classify changes into material topics and mechanical derivatives. The Skill drafts an imperative subject, verified reference lines, and one section per material topic.

Does this work with the GitHub CLI for private repositories?

Yes, it uses standard gh commands like gh pr view and gh api to fetch PR data, comments, and reviews. Any repository accessible with your authenticated GitHub CLI session can be inspected.

Why does the commit message include Co-authored-by trailers?

Trailers credit commit authors, co-author trailer entries, and reviewers whose feedback shaped the final change. Each email is verified against commit data or the GitHub API; unverifiable contributors are reported as missing context instead of guessed.

What are the limitations of automated commit message generation?

The message quality depends on available PR evidence; sparse PRs without descriptions or reviews yield thinner narratives. Quantified or causal claims that cannot be verified against sources are narrowed or omitted rather than asserted.