generate-changelog-zh-tw

Generate a Traditional Chinese changelog section from Git commit history.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/CloudyWing/ai-dotfiles --skill generate-changelog-zh-tw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-changelog-zh-tw
Source: https://github.com/CloudyWing/ai-dotfiles/tree/main/skills/generate-changelog-zh-tw
Command: npx skills add https://github.com/CloudyWing/ai-dotfiles --skill generate-changelog-zh-tw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates creation of a Traditional Chinese CHANGELOG section from Git commit history to remove manual aggregation, inconsistent formatting, and human error when preparing release notes.

Core Features & Use Cases

  • Version inference: Determines the next version via branch naming conventions or latest Git tag following MinVer rules.
  • Commit classification: Parses Conventional Commits to group entries into New Features, Bug Fixes, Improvements, and BREAKING CHANGE sections, then formats entries in Traditional Chinese.
  • Use case: Generate a release changelog section summarizing all visible user-facing changes since the last tag to insert into CHANGELOG.md before a release.

Quick Start

Invoke the skill with /generate-changelog-zh-tw optionally followed by the target version to produce and insert the changelog section into CHANGELOG.md.

Frequently Asked Questions about generate-changelog-zh-tw

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

FAQPage Schema
How do I generate a Traditional Chinese changelog from Git commit history?

To generate a Traditional Chinese changelog, this Skill parses your repository's Git commit history and summarizes changes between tags or branches into formatted release notes. It classifies Conventional Commits into categories and inserts a dated version section into CHANGELOG.md.

How does Conventional Commits classification work for changelog generation?

Conventional Commits classification parses commit messages to group changes into New Features, Bug Fixes, Improvements, and BREAKING CHANGE sections. This automated parsing removes manual aggregation and formatting errors when preparing release notes for your project.

Can I infer the next semantic version from branch names or Git tags using MinVer?

Yes, you can infer the next semantic version from branch naming conventions or the latest Git tag following MinVer rules. The Skill determines the appropriate version number and applies it to the generated changelog section before insertion into CHANGELOG.md.

What's the best way to maintain a changelog for projects using Conventional Commits and MinVer?

The best way to maintain a changelog is automating the aggregation of visible user-facing changes since the last tag. This Skill formats entries in Traditional Chinese and inserts a vMAJOR.MINOR.PATCH dated section directly into your CHANGELOG.md file before releases.

Does this changelog generator require specific Git branch naming conventions to infer versions?

It supports version inference through both branch naming conventions and the latest Git tag under MinVer rules. You can optionally specify the target version directly when invoking the Skill to bypass automatic inference.

What are the limitations of generating Traditional Chinese changelogs from Git history?

This changelog generation relies on strict Conventional Commits formatting to classify entries into Traditional Chinese categories. Projects with inconsistent commit messages or not using MinVer for versioning may not produce accurately grouped or versioned release notes.