Write or improve high-signal PR merge commit messages and squash commit messages. Use this whenever the user says "create a commit message for this PR", "write a merge commit message", "draft the squash commit body", "improve this commit message", or asks for a message that preserves the why behind a pull request. This skill inspects the PR, linked issues, and code changes so the final commit message is readable and useful from git history alone.
Write commit messages that preserve the reason for the change, not just the diff.
A strong merge commit message should let a future maintainer answer:
Use this skill for merge commits, squash commits, and "please write a better commit message for this PR" requests.
For calibration and examples drawn from Jon Pryor's commit history in dotnet/android,
see references/pryor-style-guide.md.
Before writing anything, inspect the available evidence:
When working inside a repo with PR context available, prefer first-party context over