changelog

Creates and maintains CHANGELOG.md in Keep a Changelog format, including adding entries and cutting releases. Use when the user asks to update the changelog, add a changelog entry, or record a release.

Quality

96%

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

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

An exemplary instruction-only skill body: terse, actionable, with explicit validation checkpoints on the destructive release operation and clean sectioning. No bundle files are needed and none are referenced, which fits the skill's scope.

Dimension	Reasoning	Score
Conciseness	The body is lean throughout — it never explains what a changelog is or how the format works, and every line (skeleton template, guardrails like "Do not guess it", "Do not tag, commit, or push unless asked") earns its place.	5 / 5
Actionability	Concrete, executable guidance throughout: a copy-paste skeleton template, the exact command `date +%F`, explicit reject/stop conditions, and precise edit operations (rename Unreleased to version-dated heading, insert fresh Unreleased above).	5 / 5
Workflow Clarity	Each operation is a clearly numbered sequence, and --release includes an explicit pre-write validation checklist (Unreleased has entries, version not present, version higher than latest) with a "stop with the reason" checkpoint; --create guards against overwriting an existing file.	5 / 5
Progressive Disclosure	Content is appropriately self-contained with well-organized sections (Usage, Skeleton, per-operation, Entry Style) and no bundle files; nothing needs to be split out for a skill of this scope, and navigation is easy.	5 / 5
	Total	20 / 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. Trigger term coverage is good but could add synonyms like "release notes" or "version bump" to reach full comprehensiveness.

Dimension	Reasoning	Score
Specificity	"Creates and maintains CHANGELOG.md in Keep a Changelog format, including adding entries and cutting releases" names four concrete lifecycle actions (create, maintain, add entries, cut releases) with comprehensive coverage of what a changelog skill does.	5 / 5
Completeness	It explicitly answers both what ("Creates and maintains CHANGELOG.md in Keep a Changelog format, including adding entries and cutting releases") and when ("Use when the user asks to update the changelog, add a changelog entry, or record a release") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"update the changelog", "add a changelog entry", and "record a release" are natural user phrases, but the description lacks common synonyms (e.g. release notes, version bump) and only mentions CHANGELOG.md without a broader term set.	4 / 5
Distinctiveness Conflict Risk	"CHANGELOG.md in Keep a Changelog format" carves a clear niche with distinct, changelog-specific triggers, leaving minimal overlap risk with other release or git skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: rikdc/ai-skills
Path: plugins/git-workflow/skills/changelog/SKILL.md
Commit: cd15778

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