← ClaudeAtlas

commit-pr-writinglisted

What a commit message, a PR title and a PR description say, and which of them lands on the default branch under GitHub's default squash merge.
Jartan-LLC/grimoire · ★ 3 · Code & Development · score 72
Install: claude install-skill Jartan-LLC/grimoire
# Commit Messages and PR Descriptions The project's own rules win where they speak. No style or brevity pass over a commit message or a PR description: keep every verification line, issue id and reason. Before you state how the code behaves when it runs (its output, what a test catches, why a result comes out as it does), run it or watch it. If you only reasoned it out, check it now or leave it out. This does not apply to what the change does or why you chose it. In a public repository, whatever the project's rules say, keep exploit and reproduction detail of a security flaw whose fix is not released out of the PR title and description and out of every commit message but the one whose diff removes the flaw, unless the text links the released fix or a public advisory. ## The Commit Message Write every commit message to land on the default branch, whatever the merge setting. Under GitHub's default squash merge, every commit message on the branch goes into the squash commit's message (merges from the base branch aside). - Say why the change was made and why this way; where alternatives were weighed, name the one a later reader would propose and why it lost. - Describe the change as merged; narrate no review rounds, requests, attempts, CI re-runs or branch history, and let the subject name the change (never "address review findings"). - Do not restate what the reader already has open: no file lists, diff retelling or test totals CI shows. - State each gap or deferral (with