Agent skill

Release Changelog Update

by afkT in afkT/DevUtils

依据目标库/模块既有 CHANGELOG.md 版式,从上一版日期到当前用 git 收集该库根路径下 提交(含完整 commit message 正文),去重合并后撰写专业变更条目;与项目发版版本 配置对齐。在用户要求更新 CHANGELOG、发版说明、模块变更记录或同步某子库 Change Log 时使用。

Apache-2.0Auto-check passedDevelopment

Install Release Changelog Update

skills CLI
$ npx skills add afkT/DevUtils --skill release-changelog-update -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install afkT/DevUtils release-changelog-update --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/afkT/DevUtils.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/release-changelog-update .claude/skills/release-changelog-update && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
release-changelog-update
GitHub stars
1.6k
Token cost
~902 tokens
SKILL.md length
205 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
Apache-2.0

At a glance

依据目标库/模块既有 CHANGELOG.md 版式,从上一版日期到当前用 git 收集该库根路径下 提交(含完整 commit message 正文),去重合并后撰写专业变更条目;与项目发版版本 配置对齐。在用户要求更新 CHANGELOG、发版说明、模块变更记录或同步某子库 Change Log 时使用。

  • Works in 4 steps: 默认以发版为准:新版本字符串以项目约定的发版版本源为准(如… → CHANGELOG 与发版配置不同步(例如 CHANGELOG 仍为… → 带连字符后缀的版本(如 2.5.1-2):下一版以维护者与发版版本源为准,不臆造… → …
  • Tasks that involve Changelog and release notes
  • SKILL.md covers 适用范围, 文件版式(与现有一致), 新版本号 and 变更时间窗与 git 范围, plus 5 more sections
  • Calls git

What it does

Release Changelog Update is an agent skill from afkT/DevUtils. 依据目标库/模块既有 CHANGELOG.md 版式,从上一版日期到当前用 git 收集该库根路径下 提交(含完整 commit message 正文),去重合并后撰写专业变更条目;与项目发版版本 配置对齐。在用户要求更新 CHANGELOG、发版说明、模块变更记录或同步某子库 Change Log 时使用。

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes and Commit messages. It works with Git. The repository describes itself as: :fire: ( 持续更新,目前含 300+ 工具类 ) DevUtils 是一个 Android 工具库,主要根据不同功能模块,封装快捷使用的工具类及 API 方法调用。该项目尽可能的便于开发人员,快捷、高效开发安全可靠的项目。 The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Changelog and release notes
  • Tasks that involve Commit messages

Example prompts

  • “/release-changelog-update”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. 默认以发版为准:新版本字符串以项目约定的发版版本源为准(如 Gradle/Maven/npm 等模块版本字段,与对外发布号一致)。用户或发版流程另有指定时以指定为准。
  2. CHANGELOG 与发版配置不同步(例如 CHANGELOG 仍为 2.5.1-2 而版本配置已为 2.5.2):写入 CHANGELOG 的 Version 必须与本次对外发布版本一致;若仅文档滞后,应对齐当前发版配置中的值并在同次提交中避免长期分叉。
  3. 带连字符后缀的版本(如 2.5.1-2):下一版以维护者与发版版本源为准,不臆造 semver;常见情况是下一正式补丁版为 2.5.2、2.5.3 等,以发版配置为准。
  4. 日期:*(yyyy-MM-dd)* 使用写入当天(对话中 authoritative date)或用户指定的发版日。

What it can do on your machine

Read from SKILL.md and the folder at commit 6022ede. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release Changelog Update loads about 902 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 205 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~902

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from afkT/DevUtils at commit 6022ede, republished under its Apache-2.0 licence (© afkT). 205 words, ~902 tokens.

Download SKILL.mdSave it as .claude/skills/release-changelog-update/SKILL.md (or your agent's skills folder).
name
release-changelog-update
description
依据目标库/模块既有 CHANGELOG.md 版式,从上一版日期到当前用 git 收集该库根路径下 提交(含完整 commit message 正文),去重合并后撰写专业变更条目;与项目发版版本 配置对齐。在用户要求更新 CHANGELOG、发版说明、模块变更记录或同步某子库 Change Log 时使用。
disable-model-invocation
true

发版 CHANGELOG 更新

适用范围

  • 目标为库根目录(或子模块根目录)下的 CHANGELOG.md;若源码分布在多个子目录但共用同一份 CHANGELOG,则以该 CHANGELOG 所在目录为库根,git 范围覆盖所有属于该库的源码路径。
  • 不得臆造版式:先 Read 目标文件顶部若干版本块,严格沿用该文件既有「Change Log」标题、下划线、Version 行、分隔线长度、条目前缀与历史语气。

文件版式(与现有一致)

markdown
Change Log
==========

Version <版本字符串> *(yyyy-MM-dd)*
----------------------------

* `[标签]` 中文说明(可含英文类名、方法名,与同文件历史条目一致)
  • 标签:只使用该文件或同仓库其它 CHANGELOG 中已出现过的标签,例如 `[Add]`、`[Delete]`、`[Update]`、`[Refactor]`、`[Move]`、`[Feature]`、`[Build]`、`[Chore]`、`[Upgrade]`、`[Fix]`、`[Merge]`、`[Remove]`、`[Perf]`、`[Style]`、`[sync]` 等;禁止自造未在仓库中出现过的标签缩写。
  • 一条一事:同类改动合并为一条;禁止把每个 commit 机械抄成一条;语义重复的条目合并后只保留一条表述。

新版本号

  1. 默认以发版为准:新版本字符串以项目约定的发版版本源为准(如 Gradle/Maven/npm 等模块版本字段,与对外发布号一致)。用户或发版流程另有指定时以指定为准。
  2. CHANGELOG 与发版配置不同步(例如 CHANGELOG 仍为 2.5.1-2 而版本配置已为 2.5.2):写入 CHANGELOG 的 Version 必须与本次对外发布版本一致;若仅文档滞后,应对齐当前发版配置中的值并在同次提交中避免长期分叉。
  3. 带连字符后缀的版本(如 2.5.1-2):下一版以维护者与发版版本源为准,不臆造 semver;常见情况是下一正式补丁版为 2.5.2、2.5.3 等,以发版配置为准。
  4. 日期:*(yyyy-MM-dd)* 使用写入当天(对话中 authoritative date)或用户指定的发版日。

变更时间窗与 git 范围

  1. 时间基准:读取 CHANGELOG 最上方已发布版本的 Version … *(yyyy-MM-dd)*,取其中日期作为「上一版发布日」。
  2. 收集区间:从该日期的 00:00 起至当前(以归纳时的仓库 HEAD 与对话日期为准),落在该库根目录下的改动;以 git 事实 为准,禁止写入未触及该路径的条目。
  3. 当日边界:若上一版当日仍有后续提交、或与「更新 CHANGELOG 的 commit」重复,可改用 --after="yyyy-MM-dd" 或定位「写入上一版 CHANGELOG 的 commit」之后继续 git log,减少重复;默认 --since="yyyy-MM-dd" 与用户约定一致即可。

必须使用「完整」commit message(勿只看第一行)

禁止仅用 git log 的 subject(%s)作为唯一依据;正文(body)、多段落说明、列表同样参与归纳。

推荐在库根路径下执行(将日期、路径替换为实际值;PATH 为库目录,如 <库根>/):

bash
# 完整提交说明:%B = subject + body(含空行与多段)
git log --since="yyyy-MM-dd" --pretty=format:"%h%n%B%n----COMMIT----" -- PATH

# 需要作者日期辅助核对时(仍含完整 %B)
git log --since="yyyy-MM-dd" --pretty=format:"%h %ad%n%B%n----COMMIT----" --date=short -- PATH
  • Merge commit:若 --no-merges 后信息量足够,可忽略 merge 噪声;若重要合并说明仅在 merge message 中,则保留并去重其与子提交的重复表述。
  • 多路径库:-- 后写多个路径,或分路径 git log 后合并同一主题的 commit,条目仍按「一条一事」归纳。

归纳、去重与文案

  1. 通读:按时间或逆序阅读每个 commit 的完整 %B(含 body、续行、列表)。
  2. 去重:同一问题多次提交、revert 再修、相同类名/方法名反复出现 → 合并为一条用户向说明;忽略完全重复的句子或同一改动的 cherry-pick 副本。
  3. 映射标签:按真实语义选 [Fix]/[Add]/[Refactor] 等,与同文件历史用法一致;不确定时优先与同库近期条目风格一致。
  4. 专业准确:技术事实与类/方法/模块名与仓库一致;说明用简短中文,必要时保留英文标识符。
  5. 插入位置:新版本块插在 ========== 之后、上一版 Version 块之前(全文从新到旧)。

变更很少或几乎无实质改动时

  • 不得编造未发生的 API/功能说明。
  • 参照该库 CHANGELOG 历史:许多子库在仅依赖升级或同步发版时会写 `[Chore]` 依赖 xxx 库同步升级(或对应依赖库名),句式与同文件历史保持一致。
  • 若区间内确无落在该路径的提交:向用户说明「无新 commit 可记」;若发版流程仍需新版本号与日期,可仅更新 Version 行与一条与历史一致的 [Chore](须与发版配置/实际依赖变更一致,不得虚构依赖升级)。

版本号来源(与库根对应)

  1. 优先使用用户指定的版本字符串或发版版本配置文件中的对应模块字段(Gradle versionName/version、Maven version、npm version 等)。
  2. 若用户未指明路径,在工作区内检索与目标模块/库名相关的版本声明(模块构建脚本、根版本清单、CI 发版变量等),不得臆造版本键名或版本号。
  3. 写入 CHANGELOG 的 Version 必须与本次对外发布版本一致;多子模块各自 CHANGELOG 时,每条记录对其库根的版本源,勿混用其它模块版本。

执行清单

  • Read 目标 CHANGELOG.md 顶部 2~3 个版本块,确认标题、标签、句式。
  • 解析上一版 Version … *(yyyy-MM-dd)* 与即将写入的新版本(对照发版版本源或用户指定)。
  • 对该库路径执行 git log,格式含完整 %B,必要时配合 git diff/git show 核对事实。
  • 合并去重后撰写条目;少变更时对齐历史 [Chore] 等写法。
  • 在文件顶部插入新版本块,不破坏下方历史结构。

© afkT, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .cursor/skills/release-changelog-update of afkT/DevUtils.

Open the folder on GitHubat commit 6022ede

Compare with similar skills

Release Changelog Update next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Release Changelog Update compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Changelog Update this skillafkT/DevUtils1.6k—~902Automated safety check: PassApache-2.0
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills104k2 repos~3.5kAutomated safety check: NotesMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Commitizencommitizen-tools/commitizen3.5k—~839Automated safety check: PassMIT
PR Pushicebear0828/codex-proxy1.8k—~2.2kAutomated safety check: NotesCustom licence

Similar skills

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    104k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes
  • Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Commitizen

    commitizen-tools/commitizen

    A skill your agent uses for tasks involving Conventional Commits, commit message validation, Commitizen configuration, semantic version bumps, changelog generation, or CI/release automation with the…

    3.5k GitHub stars~839 tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • PR Push

    icebear0828/codex-proxy

    Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…

    1.8k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check: notes
  • PR Push

    icebear0828/codex-proxy

    Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…

    1.8k GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check: notes

More from afkT/DevUtils

All 13 skills in this repo
  • 依据 Android 官方「版本」文档完成平台适配:按版本号 N 抓取行为变更(所有应用、 targetSdk=N)、changes/features 子页与探索新功能/API;归纳影响项并落地到 Manifest/Gradle/工具类封装。在用户要求 Android 版本适配、行为变更排查、 targetSdk 升级、新 API 封装或对照…

    1.6k GitHub stars~1.8k tokensUpdated 1 mo ago
    Auto-check passed
  • 统一 Android XML 资源命名:layout、drawable、mipmap、color、values、id 的前缀与 snakecase 规则;把颜色/圆角/描边/状态编码进文件名(bg、border、textcolor…selector)。

    1.6k GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed
  • 根据用户给出的 Java/Kotlin 工具类或 View 相关源码,设计并实现 androidx.databinding.BindingAdapter。

    1.6k GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed
  • 对 DevUtils 工程(DEPSROOT=file/gradle、DEPSMANIFEST=file/deps)中定义的第三方库 GAV 依赖做版本查证与升级;结合 Maven Central、Google Maven、Gradle Plugin Portal、 JitPack 与 GitHub Releases/README 交叉校验「最新可用版本」;必要时修正…

    1.6k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • 为布局 XML 中的控件默认补全 DevSimple(lib/DevSimple)的 ViewTheme 样式引用: 按控件继承链匹配 ViewTheme.&lt;类名&gt;,ImageView/AppCompatImageView 使用 ViewTheme.ImageView.FITXY,无匹配则用 ViewTheme.View。工作区内优先 Read…

    1.6k GitHub stars~727 tokensUpdated 1 mo ago
    Auto-check passed
  • UI Devwidget Round

    afkT/DevUtils

    在需要圆角矩形纯色背景、描边边框时,优先用 DevWidget(io.github.afkt:DevWidgetX)的 dev.widget.ui.round 包替代 shape / layer-list drawable。流程与核心坑在 SKILL,Round 系列 View、R.styleable.DevWidget 中 app:dev 属性及源码对照见…

    1.6k GitHub stars~880 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Release Changelog Update

What does Release Changelog Update do?

依据目标库/模块既有 CHANGELOG.md 版式,从上一版日期到当前用 git 收集该库根路径下 提交(含完整 commit message 正文),去重合并后撰写专业变更条目;与项目发版版本 配置对齐。在用户要求更新 CHANGELOG、发版说明、模块变更记录或同步某子库 Change Log 时使用。. Release Changelog Update is an agent skill from afkT/DevUtils.

When should I use Release Changelog Update?

Release Changelog Update fits situations like: tasks that involve Changelog and release notes; tasks that involve Commit messages.

How do I install Release Changelog Update in Claude Code?

Run `npx skills add afkT/DevUtils --skill release-changelog-update -a claude-code`. Or copy the skill folder (.cursor/skills/release-changelog-update in afkT/DevUtils) into .claude/skills/release-changelog-update in your project. Claude Code loads it when a task matches its description.

How do I install Release Changelog Update in Codex?

Run `npx skills add afkT/DevUtils --skill release-changelog-update -a codex`. Or copy the skill folder (.cursor/skills/release-changelog-update in afkT/DevUtils) into .agents/skills/release-changelog-update in your project. Codex loads it when a task matches its description.

Can I use Release Changelog Update in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add afkT/DevUtils --skill release-changelog-update -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-changelog-update, .gemini/skills/release-changelog-update, .github/skills/release-changelog-update and .opencode/skills/release-changelog-update in your project.

What does Release Changelog Update need to run?

Going by SKILL.md and its folder, Release Changelog Update needs the command-line tools its instructions call (git).

Does Release Changelog Update access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Release Changelog Update safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Release Changelog Update use?

Release Changelog Update is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release Changelog Update use?

About 902 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release Changelog Update?

Skills that share tags, products or a category with Release Changelog Update: React Router Release Notes Prep (remix-run/react-router, 57k stars), Git Workflow and Versioning (addyosmani/agent-skills, 104k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Commitizen (commitizen-tools/commitizen, 3.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Changelog Update?

afkT (a GitHub user) maintains it in afkT/DevUtils, which has 1,613 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on September 2, 2026.

Source: afkT/DevUtils on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.