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

90%

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-5

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

The body is concise, actionable, and well-structured for a simple git-driven skill. The single meaningful gap is the absence of a verification checkpoint despite this being a batch edit of a tracked file, which caps workflow clarity.

Suggestions

Add an explicit validation step to the workflow, e.g. after inserting entries, confirm no duplicate hashes already exist in Unreleased and that any PR links resolve before finishing.

Specify how to handle commit summaries that are noisy or non-user-facing (the rule says 'skip... when clearly non-user-facing and explain') but gives no concrete detection heuristic, leaving that step under-specified.

Clarify the fallback when 'git describe --tags --abbrev=0' fails or the repo has tags pointing at non-release commits, since step 1's fallback ('search recent history for a release commit') lacks a concrete command.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with zero padding: it does not explain git or CHANGELOG concepts and every line is a concrete command or rule, assuming Claude's competence.	5 / 5
Actionability	Fully executable throughout — concrete commands ('git describe --tags --abbrev=0', 'git log <base>..HEAD --reverse --format=...', 'gh pr list --search ...') and a precise entry format '- [<short-hash>](<url>) <one-line summary>' covering the common cases.	5 / 5
Workflow Clarity	A clear 5-step sequence exists, but this is a batch edit of CHANGELOG.md with no explicit validation/verification checkpoint (e.g., confirm no duplicate entries, verify PR links resolve), so the batch-operation cap holds it at 3.	3 / 5
Progressive Disclosure	Under 50 lines, single-purpose, no external references needed, and cleanly organized into Workflow and Rules sections — matching the simple-skill exception for a top score.	5 / 5
	Total	18 / 20 Passed

Description

92%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, specific description that clearly states both capability and trigger conditions in third person. The only soft spot is trigger-term breadth, which covers the natural phrasings but lacks synonyms and file-extension cues.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions: 'Update CHANGELOG.md Unreleased items from git commits since the latest release', 'one concise line per commit and commit/PR links' — comprehensive coverage matching the 5 anchor.	5 / 5
Completeness	Explicitly answers both 'what' (update Unreleased items from commits since latest release, one line per commit with commit/PR links) and 'when' ('Use when users ask to update changelog/release notes from recent commits') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say — 'update changelog/release notes from recent commits' — but is missing some common synonyms/variants (e.g., 'what's new'), landing at good-but-not-comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	A clear niche (CHANGELOG.md Unreleased entries from git commits) with distinct triggers ('changelog/release notes', 'recent commits', 'latest release') and minimal overlap risk with other skills.	5 / 5
	Total	19 / 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: d56e554

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