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.