lina-community-release-changelog

What problem does it solve?

Manually compiling accurate, comprehensive bilingual release changelogs for LinaPro is time-consuming and prone to errors, especially when ensuring consistent coverage of code changes, bug fixes, database schema updates, and plugin modifications across English and Chinese versions.

Core Features & Use Cases

• Evidence-based changelog generation: Collects change evidence from Git history, source code diffs, OpenSpec documents, and GitHub bug-labeled issues to avoid missing critical updates.
• Strict classification and bilingual consistency: Enforces fixed chapter structure for Highlights, Improvements, Bug Fixes, Database Changes, and Tooling changes, with full factual alignment between English and Chinese content.
• Safe manual execution: Restricts all operations to read-only checks and writing only to the ignored localdocs/changelog.md file, with no automatic triggering or modification of version control files.
• Use Case: LinaPro release managers can use this skill to generate standardized, publication-ready bilingual changelogs for new versions without risking accidental code commits or release automation triggers.

Quick Start

Use the lina-community-release-changelog skill to generate a complete bilingual changelog for the current LinaPro version and save it to localdocs/changelog.md.