lina-community-release-changelog

Compile bilingual release changelogs from Git history and GitHub issues.

147|28|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/linaproai/linapro --skill lina-community-release-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lina-community-release-changelog
Source: https://github.com/linaproai/linapro/tree/main/.agents/skills/lina-community-release-changelog
Command: npx skills add https://github.com/linaproai/linapro --skill lina-community-release-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about lina-community-release-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a bilingual release changelog from Git history and GitHub issues?

You generate a bilingual release changelog by collecting evidence from Git history, source code diffs, OpenSpec documents, and GitHub bug-labeled issues. This Skill compiles that data into a standardized dual-language changelog covering all code changes and bug fixes.

What is the best way to compile release notes for a framework with database schema updates?

The best way to compile release notes with database schema updates is using strict classification. This Skill enforces fixed structures for Highlights, Improvements, Bug Fixes, Database Changes, and Tooling, ensuring factual alignment across English and Chinese.

How does bilingual changelog generation ensure factual consistency between English and Chinese versions?

Bilingual changelog generation ensures factual consistency by enforcing strict chapter structures and aligning technical evidence across both languages. It captures code diffs, database changes, and plugin submodule modifications to prevent missing critical updates in English or Chinese.

Can I generate publication-ready changelogs without triggering automatic version releases or modifying code?

Yes, you can generate publication-ready changelogs without triggering automatic releases. This Skill restricts operations to read-only checks and writes exclusively to the ignored localdocs/changelog.md file, preventing accidental code commits or release automation triggers.

Does manual changelog generation work for plugin submodule modifications and OpenSpec documents?

Manual changelog generation works for plugin submodule modifications and OpenSpec documents. It extracts evidence from these sources alongside Git history and GitHub issues to produce comprehensive bilingual release notes for your framework versions.