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

63%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/changelog-automation/SKILL.md

Quality

Content

43%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 and well-organized as an overview, but it lacks actionable specifics (no code, commands, or named tools) and its single progressive-disclosure reference points to a file that is not present in the bundle. Generic instructions and missing validation checkpoints further weaken execution guidance.

Suggestions

Add concrete, executable guidance: name specific tools (e.g. changeset/conventional-changelog/semantic-release) and include a minimal copy-paste command or config snippet for the common case.

Fix or remove the reference to 'resources/implementation-playbook.md' — either add the file to the bundle or inline the key patterns, templates, and examples so the pointer resolves.

Make the workflow explicit with validation checkpoints (e.g. generate notes -> review for secrets/internal details -> verify against commits -> publish) rather than a flat list of generic steps.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of padding or explanations of concepts Claude already knows, though a few generic instructions ('Select a changelog format', 'Configure tooling') could be tightened with concrete defaults.	4 / 5
Actionability	Guidance is high-level and abstract ('Select a changelog format and versioning strategy', 'Configure tooling to generate and publish notes') with no concrete code, commands, or tool names, leaving the executor without specific steps.	2 / 5
Workflow Clarity	A rough sequence is present in 'Instructions', but steps are generic and lack validation checkpoints; the Safety section mentions reviewing output but no verify-fix-retry loop is explicit, and batch/destructive-publish operations cap it at 3.	3 / 5
Progressive Disclosure	Structure is present but the only detailed reference, 'resources/implementation-playbook.md', does not exist in the bundle, so the signaled one-level-deep reference is broken and core detail has nowhere to live.	2 / 5
	Total	11 / 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 capabilities and explicit trigger conditions in third person, with concrete domain actions and a recognizable format standard. Minor gaps in tool specificity and synonym coverage keep it just below a perfect score on some dimensions.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Automate changelog generation from commits, PRs, and releases', 'Keep a Changelog format') but stops short of naming tools or more granular actions, leaving minor coverage gaps.	4 / 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	Good natural keyword coverage ('release workflows', 'release notes', 'commit conventions', 'changelog') with phrases users would say, but misses common synonyms like 'release notes' variants and file/format extensions.	4 / 5
Distinctiveness Conflict Risk	Clear changelog/release-notes niche with distinct triggers, but 'standardizing commit conventions' has minor overlap risk with general commit-message skills.	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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/changelog-automation/SKILL.md
Commit: 1f67c44

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