From 3f2bea8204760d6f9a1a1ccfcffeab51f17c0380 Mon Sep 17 00:00:00 2001 From: jnasbyupgrade Date: Sun, 9 Aug 2026 15:17:25 -0500 Subject: [PATCH] Fix incorrect claim about how GitHub builds squash commit messages GitHub doesn't auto-build a squash commit message from a PR description; the maintainer manually copies the opening into it, which is what the hard-wrap rule actually depends on. ai/PR.md's own general no-hard-wrap rule has the same fix. --- CLAUDE.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index ed1efd7..8911420 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -83,8 +83,9 @@ Write it accordingly: - Do NOT add a marker delimiting the "commit message" from "the rest". Just let the opening carry its own weight, with any extra context following after it. - Do NOT hard-wrap paragraphs: write each paragraph as a single long line (blank line - between paragraphs). Hard-wrapping at ~80 columns conflicts with how GitHub builds the - squash commit message from the description. + between paragraphs). The maintainer copies the opening more or less directly into the + squash commit message; hard-wrapped line breaks would carry over into that commit + message too. - Length past the opening is fine — backstory and detail are often worth keeping. Being hard to *scan* is the actual problem: if there's enough detail to justify it, give the rest real structure (headers, bullet lists, separate sections for "what changed" vs.