changelog

AI DevKit · Update CHANGELOG.md Unreleased items from git commits since the latest release. Use when users ask to update changelog/release notes from recent commits, with one concise line per commit and commit/PR links.

Quality

93%

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

87%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.

The body is an efficient, highly actionable changelog procedure with executable git/gh commands and a concrete output format. Its only real gap is the absence of an explicit validation or verification checkpoint after the batch edit, which caps workflow clarity.

Suggestions

Add a final verification step, e.g. re-run `git log <base>..HEAD --oneline` and confirm the count matches the lines inserted into the Unreleased section, to close the validation gap for the batch edit.

Include a brief rollback/undo note (e.g. `git checkout -- CHANGELOG.md` if the inserted lines are wrong) as a feedback loop for error recovery.

State explicitly what to do when a commit subject is ambiguous (no PR marker and `gh pr list` returns nothing) so the PR-link decision is fully deterministic.

Dimension	Reasoning	Score
Conciseness	At roughly 30 lines the body is lean and assumes Claude's competence, with no over-explanation of git or changelog concepts; every line is instruction, matching the lean-and-efficient anchor.	3 / 3
Actionability	Provides copy-paste-ready, executable commands ("git describe --tags --abbrev=0", "git log <base>..HEAD --reverse --format='%H%x09%s'", "gh pr list --search <hash> --state all --json number,url") plus a concrete line format spec, satisfying the fully-executable anchor.	3 / 3
Workflow Clarity	The five-step workflow is clearly sequenced with sensible conditional fallbacks (no tags, no Unreleased section, PR detection), but it lacks any explicit validation/verification checkpoint for a batch file edit, so per the rubric's batch-operation cap it cannot reach 3.	2 / 3
Progressive Disclosure	A sub-50-line, single-purpose skill with no need for external references and clean Workflow/Rules sections qualifies for the top anchor under the simple-skills scoring note.	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, concise description that states concrete capabilities, includes natural trigger terms, answers both what and when explicitly, and occupies a distinct niche. It avoids fluff and uses appropriate third-person/imperative voice.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "Update CHANGELOG.md Unreleased items from git commits since the latest release" with "one concise line per commit and commit/PR links" — matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (update Unreleased items from commits, one line per commit, with links) and when ("Use when users ask to update changelog/release notes from recent commits") with an explicit trigger clause.	3 / 3
Trigger Term Quality	"Use when users ask to update changelog/release notes from recent commits" surfaces natural terms (changelog, release notes, recent commits) a user would actually say, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	The narrow niche of rebuilding a changelog from git commits with specific triggers is unlikely to fire for unrelated skills, fitting the clear-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: codeaholicguy/ai-devkit
Path: skills/changelog/SKILL.md
Commit: 15b09d2

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.