release-changelog-update

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

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable single-file skill with executable git commands, a concrete format template, and a sequenced checklist with verification. Its main weakness is redundant coverage of version sourcing and repeated injunctions that could be tightened.

Suggestions

Merge the overlapping "新版本号" and "版本号来源（与库根对应）" sections into one, since both restate that the Version must match the release config and forbid fabricating version numbers.

Consolidate recurring injunctions ("不得臆造"/"不得编造" and "一条一事") so each rule is stated once and cross-referenced rather than repeated across sections.

Tighten the label vocabulary list by referencing the existing-file convention once instead of enumerating every tag inline, trimming tokens without losing the guidance.

Dimension	Reasoning	Score
Conciseness	The body is instruction-dense and avoids explaining concepts Claude already knows, but version sourcing is duplicated across "新版本号" and "版本号来源" and injunctions like "不得臆造"/"一条一事" recur, so it is mostly efficient rather than lean.	2 / 3
Actionability	Provides fully executable git commands with real format strings (e.g. git log --pretty=format:"%h%n%B%n----COMMIT----" plus --date=short/--since/--after), a concrete CHANGELOG template, and an exact insertion rule, all copy-paste ready with marked placeholders.	3 / 3
Workflow Clarity	A sequenced 执行清单 checklist with a fact-verification checkpoint ("git diff/git show 核对事实") and an explicit low-change decision branch (inform user "无新 commit 可记") gives clear sequence and validation; the single-file top-insert is low-risk so the destructive/batch cap does not apply.	3 / 3
Progressive Disclosure	No bundle files exist and the skill is a single self-contained, well-sectioned document with no nested references; per the rubric's simple-skill note this organization earns a 3.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that states concrete capabilities and an explicit trigger clause, covering both what the skill does and when to invoke it. It is distinct and unlikely to mis-trigger.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "用 git 收集该库根路径下提交（含完整 commit message 正文）", "去重合并后撰写专业变更条目", "与项目发版版本配置对齐" — matching the 'multiple specific concrete actions' anchor rather than the partial-coverage anchor at 2.	3 / 3
Completeness	Answers both what (collect/dedupe/write/align) and when via the explicit trigger "在用户要求更新 CHANGELOG、发版说明、模块变更记录或同步某子库 Change Log 时使用", so the missing-Use-when cap at 2 does not apply.	3 / 3
Trigger Term Quality	Covers natural phrasings a user would say — "更新 CHANGELOG", "发版说明", "模块变更记录", "同步某子库 Change Log" — giving good coverage rather than just some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (per-format CHANGELOG updates sourced from git and aligned to release version config) with distinct triggers, making conflict with other skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: afkT/DevUtils
Path: .cursor/skills/release-changelog-update/SKILL.md
Commit: 3fa9400

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.