changelog-automation

Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/documentation-generation/skills/changelog-automation/SKILL.md

Quality

Content

61%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 well-structured with a clear reference pointer and solid executable commit/changelog examples, but it leans verbose and lacks a sequenced workflow with validation checkpoints for its automated-release use case. A broken markdown code fence also lets example content leak into the prose structure.

Suggestions

Close the ```markdown code fence (opened before the 'Keep a Changelog Format' header) so the Summary/Highlights/Commit-Message sections render as prose/examples rather than being trapped inside one code block.

Add a short sequenced workflow with an explicit validation checkpoint (e.g. lint commits with commitlint -> generate changelog -> verify generated entries -> tag/release) to support the batch/automated operations the skill describes.

Trim the illustrative sample changelog narrative and Do/Don't lists, or move them to references/details.md, to reduce tokens spent on concepts Claude already knows.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the inlined sample changelog narrative (dark mode/checkout story), dependency tables, and Do/Don't lists restate concepts Claude already knows and could be trimmed or moved to references.	3 / 5
Actionability	Provides copy-paste-ready commit message examples and a full Keep a Changelog template; the actual generation tooling/commands live in references rather than the body, leaving minor gaps.	4 / 5
Workflow Clarity	Content is organized as concepts and examples rather than a sequenced multi-step workflow, and the body lacks any validate->fix->retry feedback loop for the batch/automated release operations it describes, capping this dimension at 3.	3 / 5
Progressive Disclosure	SKILL.md serves as an overview with a one-level-deep, clearly-signaled reference (references/details.md, 'Read that file when the navigation tier above is insufficient'), and the referenced file exists; minor gaps remain from inlined example content and a broken code fence.	4 / 5
	Total	14 / 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.

The description is strong: it states concrete capabilities and provides explicit, natural 'Use when...' trigger guidance covering the main scenarios. It is specific, complete, and clearly distinct from neighboring skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Automate changelog generation from commits, PRs, and releases', 'following Keep a Changelog format'), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both what ('Automate changelog generation... following Keep a Changelog format') and when ('Use when setting up release workflows, generating release notes, or standardizing commit conventions') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural triggers ('release workflows', 'release notes', 'commit conventions', 'commits, PRs, releases') but a few common synonyms (e.g. 'CHANGELOG', 'semantic versioning', 'semver') are missing, so it sits above the midpoint rather than at comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (changelog/release-notes automation) with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	19 / 20 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: wshobson/agents
Path: plugins/documentation-generation/skills/changelog-automation/SKILL.md
Commit: d6837ae

Reviewed: about 12 hours 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.