generate-release-notes

Generate Release Notes

Generate platform-specific, bilingual release notes from the latest entry in CHANGELOG.md using generate-release-notes.py. Produces separate output files per platform with enforced character limits and user-friendly language.

Prerequisites

• CHANGELOG.md must exist with at least one version entry — run the generate-changelog skill first if needed
• Python 3 (standard library only, no pip install)
• Settings at .claude/changelog-manager.local.md — run /changelog-manager:changelog-config if missing

Platform Reference

Platform	Output File	Char Limit	Tone
playstore	RELEASE_NOTES_PLAYSTORE	500 per language	Concise, bullet-first
appstore	RELEASE_NOTES_APPSTORE	4,000 per language	Friendly, feature-rich
web	RELEASE_NOTES	No limit	Detailed, full context

Workflow

Step 1: Read Settings

Read .claude/changelog-manager.local.md. If it does not exist, use defaults and notify the user:

languages:
  - code: en
    name: English
platforms:
  - web

Step 2: Read CHANGELOG.md

Read the latest version block (the first ## [vX.Y.Z] section). Extract:

• Version number and release date
• All categorized entries by section (Breaking Changes, Added, Changed, Fixed, Reverted)

Step 3: Generate Per-Platform Notes

For each platform in settings, build and run one command with all language blocks:

python3 $CLAUDE_PLUGIN_ROOT/scripts/generate-release-notes.py \
  --platform <platform> \
  --lang <code1> --intro "<intro1>" --items "<items1>" \
  --lang <code2> --intro "<intro2>" --items "<items2>"

Writing the --intro

The intro must be at least 100 characters (enforced by the script), at most 2 sentences, friendly, and free of technical terms. Include the version number or release context. Translate faithfully per language.

Writing the --items

Convert CHANGELOG entries to user-friendly, non-technical language. Format as "- First change\n- Second change". Translate each item per language — non-English items are not validated against CHANGELOG.

Platform-specific item count:

Platform	Recommended Items
playstore	3–5 (must fit 500 chars including intro)
appstore	5–10 (can expand on key features)
web	All significant changes, full detail

For Play Store, prioritize: Breaking Changes > Added > Fixed > Changed > Reverted.

For tone guidelines, language examples, and localization tips per language, see references/platform-guide.md.

Step 4: Handle Errors

Character limit exceeded (Play Store / App Store):

1. Shorten the intro (reduce to 1 sentence, aim for ~110–120 chars)
2. Remove lowest-priority items (Reverted → Changed → Fixed)
3. Shorten remaining item text
4. Re-run the script

Intro too short (under 100 chars):

• Expand the intro to be more descriptive and welcoming
• Add context about what the release focuses on

Step 5: Report to User

Summarize:

• Platform(s) and output file(s) written
• Languages generated
• Character count per language (critical for Play Store)
• Any items omitted due to character limits

Additional Resources

• references/platform-guide.md — Tone guidelines, writing examples per platform, and localization tips
• examples/playstore-bilingual.md — Complete worked example: Play Store with English + Indonesian output