release-note-publisher

To generate bilingual release notes from commit history, this Skill converts release-branch commits into aligned English and Chinese text. It drafts user-facing updates locally under dev-docs, ensuring both language sections stay in sync before publishing.

Yes, you can publish drafted release notes directly to GitHub Releases. The Skill uses the local H1 heading as the release title and pushes the finalized bilingual content to the GitHub platform automatically.

To keep English and Chinese sections aligned when editing release notes, the Skill enforces a synchronized bilingual structure. It ensures that any modifications made to one language section are reflected in the other, maintaining consistent user-facing updates.

Yes, this release note publisher works without external dependencies. It operates independently using internal scripts and references to parse commit history and format the output, requiring no additional packages or libraries to function.

The best way to automate bilingual changelog generation for a release branch is using a dedicated publisher Skill. It extracts commits, drafts aligned English and Chinese updates locally, and publishes them to GitHub Releases, reducing manual drafting time.