From 50838832d439a974f232fda6726d2c576d0552f6 Mon Sep 17 00:00:00 2001 From: rzen Date: Sat, 20 Jun 2026 19:12:44 -0400 Subject: [PATCH] Sharpen changelog rule: only end-user-meaningful changes Claude-Session: https://claude.ai/code/session_01A9CfUa4E9Zd5swfoNsYPs7 --- CLAUDE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index 8f7f30d..4e6205c 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -96,6 +96,6 @@ Seeded on demand, never automatically — an empty cache at launch is indistingu - Group entries by month, newest month first; a version milestone (e.g. **2.0**) may prefix the entry it applies to. - Write each entry as its own blank-line-separated paragraph — **no bullet or dash markers**, because the Apple inline-Markdown subset IndieAbout renders doesn't style them (see the `indie-about` skill for the supported subset). - Derive entries from the git log, but rewrite (don't copy) each into a concise, end-user-understandable description of the crux of the change. -- Include only changes significant to an end user; skip internal / tooling / refactor-only commits. In particular, never log changes to the changelog itself (its preamble, formatting, or how it's derived) — these have zero end-user value. +- Include only changes with substantive meaning for an end user — app behavior, new features, and the like. Skip anything else (internal / tooling / refactor / docs-only commits). - When one commit holds several user-facing changes, split them into separate paragraphs. - When several commits address the same user-facing change, collapse them into one paragraph.