From cdeba547bfa158e57dfedafe896a715d0d07e7af Mon Sep 17 00:00:00 2001 From: Evan Vetere Date: Tue, 28 Jul 2026 13:03:01 -0400 Subject: [PATCH] docs: scope 80-char hard-wrap to commit messages The commit-message format section said "hard wrap at 80 characters" with no stated scope, so the rule got applied to GitHub issue and PR bodies too. Those render as GitHub-flavored markdown and soft-wrap on their own; hard wrapping them produces ragged output in the web UI and fights the editor when someone revises the text. State the scope explicitly, matching the equivalent rule in the infra repo's CLAUDE.md. Key changes: - Add a Scope bullet limiting the 80-char hard-wrap to commit messages - Call out that PR descriptions, issues, and comments must not be hard-wrapped, breaking lines only where markdown requires it --- CLAUDE.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index e9a8034d..f7c80b2e 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -193,3 +193,7 @@ Key changes: - **Commit types**: feat, fix, refactor, docs, test, chore, perf, style, ci - **No watermarks** or co-author tags - **Focus on what/why**, not how +- **Scope**: the 80-char hard-wrap applies to commit messages only. PR + descriptions, GitHub issues, and comments render as GitHub-flavored markdown — + do not hard-wrap them; let prose reflow naturally and only break lines where + markdown needs it (lists, tables, code fences).