starcat-update-changelog

Update Starcat Changelog

Read ALL git commits from the main Starcat project since the last version tag, then update CHANGELOG.md (English) and CHANGELOG-ZH.md (Chinese) in supports/starcat-pro/.

File Locations

File	Path
Changelog (EN)	supports/starcat-pro/CHANGELOG.md
Changelog (ZH)	supports/starcat-pro/CHANGELOG-ZH.md
Git repo (source)	Starcat root (the Xcode project)

---

Step 0: Ask for Version Number (MANDATORY — Do This FIRST)

This is a blocking step. Before reading any git log or touching any file, you MUST know the target version number. If the user did not provide one in their invocation, immediately ask:

"Which version number should I use for this changelog entry? (e.g., 1.2.0, 1.1.1)"

Do NOT proceed to Step 1 until the user answers. Do NOT guess or assume a version number.

If the user's invocation already includes a version number (e.g., "update changelog for 1.2.0"), validate that it matches X.Y.Z format. If it doesn't, ask the user to provide a valid format.

The version number must be in X.Y.Z format (semantic versioning) because release-direct.sh requires this format.

---

Step 1: Determine Commit Range

# Latest tag
git tag --sort=-creatordate | head -1

# All commits since that tag (NO filtering, NO skip)
git log <latest-tag>..HEAD --oneline --no-merges

# Count
git log <latest-tag>..HEAD --oneline --no-merges | wc -l

If no tag exists, start from the first commit.

If there are 0 commits since the latest tag, stop and tell the user: "No new commits since . There's nothing to add to the changelog."

---

Step 2: Read EVERY Commit Message (Do NOT Skip Any)

# Full messages for ALL non-merge commits — every single one
git log <latest-tag>..HEAD --format="---COMMIT---%n%h%n%s%n%b" --no-merges

Critical rule: Read EVERY commit first. Then in Step 3a, filter out non-user-facing changes. Don't skip commits at read time — some commits with non-standard prefixes may still describe user-visible changes. The filtering happens AFTER reading, based on content.