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

84%

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

80%Weight 40%Scale 1-5

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

A lean, highly actionable skill body that respects token budget and gives exact commands and formatting rules. Its one real weakness is the absence of any verification checkpoint in a batch workflow that appends entries to a tracked file, which caps workflow clarity despite the otherwise excellent sequencing.

Suggestions

Add a final verification step, e.g., confirm the number of new Unreleased entries matches the commit count from step 2 and that no duplicate entries from a previous run already exist.

Show how to build the link targets from the repo URL (e.g., <url>/commit/<hash> and <url>/pull/<number>) so the format template is fully executable.

Include one worked example of a finished changelog line (hash link + summary) to anchor the expected output style.

Dimension	Reasoning	Score
Conciseness	The 28-line body gives raw git commands ("git log <base>..HEAD --reverse --format='%H%x09%s'") with no explanation of git itself, no padding, and no concepts Claude already knows. Every line earns its place, matching anchor 5.	5 / 5
Actionability	Concrete copy-paste commands are provided ("git describe --tags --abbrev=0", "gh pr list --search <hash> --state all --json number,url") plus an explicit line format template ("- [<short-hash>](<url>) <one-line summary>"). The gap keeping it below anchor 5: it never shows how to construct the commit or PR URL from the repo URL, and there is no worked example of a finished changelog line.	4 / 5
Workflow Clarity	The 5-step sequence is clear and includes good fallbacks ("If there are no tags, search recent history for a release commit", "If no Unreleased section exists, create one at the top"). However, this is a batch operation (one entry per commit written into a file) with no validation step — no check that entry count matches commit count or that duplicate entries from a prior run are avoided — so the rubric's batch-operation cap limits workflow clarity to anchor 3.	3 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external references, and is well organized into "## Workflow" and "## Rules" sections with a clear top summary line. Per the rubric's simple-skill guideline, this matches anchor 5.	5 / 5
	Total	17 / 20 Passed

Description

83%Weight 40%Scale 1-5

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 description that clearly states both capability and explicit trigger conditions with concrete output format details. The main risks are minor trigger overlap with commit-message skills and a slightly noisy "AI DevKit ·" brand prefix that adds no retrieval value.

Suggestions

Add one or two natural trigger synonyms such as "add recent commits to the changelog" or "what's changed since the last release" to broaden trigger coverage.

Drop the "AI DevKit ·" prefix or replace it with a capability word, since it consumes description budget without improving trigger matching.

Dimension	Reasoning	Score
Specificity	"Update CHANGELOG.md Unreleased items from git commits since the latest release" plus "one concise line per commit and commit/PR links" names several concrete actions (scoping commits to the latest release, one line per commit, linking to commits/PRs), with minor gaps such as creating the section if absent. It goes beyond the 1-2 actions of anchor 3 but is not fully comprehensive enough for anchor 5.	4 / 5
Completeness	The description explicitly answers what it does ("Update CHANGELOG.md Unreleased items from git commits since the latest release... one concise line per commit and commit/PR links") and when to use it ("Use when users ask to update changelog/release notes from recent commits") with concrete trigger phrases, matching anchor 5. The 'when' clause is explicit and specific, so anchor 4 does not fit.	5 / 5
Trigger Term Quality	"changelog", "release notes", and "recent commits" are natural phrases a user would say when needing this skill, giving good keyword coverage. A few natural variants are missing (e.g., "what's changed", "add entries to the changelog"), keeping it below anchor 5.	4 / 5
Distinctiveness Conflict Risk	"update changelog/release notes" carves out a clear niche, but the "recent commits" phrasing creates minor overlap risk with closely related commit-message-writing skills. This matches anchor 4 (mostly distinct, minor overlap) rather than anchor 5's minimal conflict risk.	4 / 5
	Total	17 / 20 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: 7ef0cd5

Reviewed: 8 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.