rzen/workouts
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

CLAUDE.md: changelog rules moved to the app-changelog skill

Browse Source 
Claude-Session: https://claude.ai/code/session_01CqrgFRh9oCeBvbpSxyw3qA
This commit is contained in:
rzen
2026-07-04 13:23:34 -04:00
parent 0c489fbbc7
commit c96b1a288b
1 changed files with 1 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+1 -9
View File
@@ -90,12 +90,4 @@ Seeded on demand, never automatically — an empty cache at launch is indistingu
## Authoring the Changelog ## Authoring the Changelog
`CHANGELOG.md` is bundled and shown in-app via IndieAbout, so write it for **end users**, not developers. When you make user-facing changes, add entries following these rules: `CHANGELOG.md` is bundled and shown in-app via IndieAbout — follow the `app-changelog` skill (single source of truth for format and workflow).
- No preamble: the file starts directly with the first month heading — no title or intro line (e.g. **Changelog** / "All notable changes…").
- 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 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.