Agent Skills › UniClipboard/UniClipboard › gen-changelog

gen-changelog

GitHub

根据 Git 历史记录生成双语（中英文）用户可见的发布更新日志，支持从指定基础标签或提交开始分析，按模板分类整理并输出到文档目录。

.agents/skills/gen-changelog/SKILL.md UniClipboard/UniClipboard

Trigger Scenarios

生成 changelog 准备 release notes 更新 docs/changelog

Install

npx skills add UniClipboard/UniClipboard --skill gen-changelog -g -y

More Options

Non-standard path

npx skills add https://github.com/UniClipboard/UniClipboard/tree/v1/.agents/skills/gen-changelog -g -y

Use without installing

npx skills use UniClipboard/UniClipboard@gen-changelog

指定 Agent (Claude Code)

npx skills add UniClipboard/UniClipboard --skill gen-changelog -a claude-code -g -y

安装 repo 全部 skill

npx skills add UniClipboard/UniClipboard --all -g -y

预览 repo 内 skill

npx skills add UniClipboard/UniClipboard --list

SKILL.md

Frontmatter

{
    "name": "gen-changelog",
    "description": "Generate bilingual, user-facing release changelogs from Git history. Use when the user asks to generate a changelog, prepare release notes, or update `docs\/changelog` for a release and provides a base tag or commit."
}

Generate Changelog

Generate the changelog for the current release.

Require a base tag or commit. Ask only when it cannot be inferred from the request or current release context.
Read docs/CHANGELOG_TEMPLATE.md for the required format and rules.
Read the current version from apps/gui-go/app.json.
Inspect commits from the base through HEAD with git log <base>..HEAD --oneline. Read full commits when the subject is insufficient.
Ignore release-cut commits and internal-only changes unless they have user-visible impact.
Consolidate entries by pull request and user-visible intent. Never repeat the same pull request in one section.
Classify entries according to the template. Every entry must end in (#<number>) taken from the squash commit.
Write English to docs/changelog/{version}.md and natural Chinese to docs/changelog/{version}.zh.md.
Include only non-empty sections, use today's date, and describe outcomes rather than implementation.
Do not copy the pinned announcement files; the release process prepends them.
Validate both files against the template and show the generated content in the result.