Generate Changelog
SkillDocs & knowledgeGenerate 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.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Generate Changelog skill
What this skill tells your AI
The instructions your AI receives, as published by uniclipboard/uniclipboard in .agents/skills/gen-changelog/SKILL.md and read by ahel’s review.
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.mdfor the required format and rules. - Read the current version from
src-tauri/tauri.conf.json. - Inspect commits from the base through
HEADwithgit 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}.mdand natural Chinese todocs/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.
If a commit has no pull request number, investigate the associated history before writing. Do not invent one.
Signals
- GitHub stars
- 2k
- Forks
- 76
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
gen-changelog- Source
- github.com/uniclipboard/uniclipboard