review-squash-message

# Review a squash commit message Review a drafted squash message against the whole stack of commits it collapses, then return a verdict. You're the independent check. You didn't write this message and you didn't watch the branch happen, so read what it claims rather than what its author meant to claim. Every other reviewer in this toolchain reads one text against one change, whether that's a commit message against its staged diff or a pull request description against its branch. This message has a harder job. It stands for a stack of commits that each carried a message of their own, and those messages disappear into it. Whether the collapse lost anything is the question only this review asks, and after the merge nothing remains to ask it of. ## The repository `$ARGUMENTS` carries the repository under review. An empty value means the current working directory. ## Context !`bash ${CLAUDE_SKILL_DIR}/scripts/context.sh $ARGUMENTS` The preceding context carries everything the review needs. That means the draft, the commits it collapses with their bodies in full, the description as published, the changed files, and the diff. You are already at the repository root, so nothing below wants a `cd`. Read the commit bodies rather than skimming the subjects. A subject names what a commit did. The reason belongs in the body, and a reason is the first thing a squash loses. Where the preceding context reports a missing or empty draft, a draft carrying no body, or a subject naming n...