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.

1.30x

Quality

74%

Does it follow best practices?

Impact

99%

1.30x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/changelog-automation/SKILL.md

The canonical home for this skill is changelog-automation in sickn33/agentic-awesome-skills

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 commendably lean and well-structured, but the Instructions are abstract rather than executable and the single referenced resource file is missing. Adding concrete tooling examples and a validation feedback loop would materially raise the score.

Suggestions

Replace abstract instruction bullets with concrete, executable guidance: name specific tools (e.g. semantic-release, standard-version, commitizen) and show example commands or config snippets for the common cases.

Add an explicit validate→fix→retry feedback loop (e.g. 'Run the generator, verify entries against the commit log, correct gaps, regenerate') so the batch changelog workflow has a real checkpoint.

Either create resources/implementation-playbook.md or remove the references to it, since the file is currently missing and the dangling link breaks progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no over-explanation of concepts Claude already knows; every section earns its place and the body assumes Claude's competence.	5 / 5
Actionability	Instructions are high-level hints — 'Select a changelog format', 'Enforce commit conventions', 'Configure tooling to generate and publish notes' — with no concrete code, commands, or named tools (e.g. semantic-release, standard-version, commitizen), missing the specific steps to execute.	2 / 5
Workflow Clarity	A rough sequence is present (select format → enforce conventions → configure tooling → review output) but validation checkpoints are only implicit; the single 'Review output' step provides no validate→fix→retry feedback loop for this batch (many-commits) operation.	3 / 5
Progressive Disclosure	Well-organized sections with a clearly signaled, one-level-deep reference to resources/implementation-playbook.md; docked one point because that referenced file does not actually exist in the bundle, leaving navigation broken.	4 / 5
	Total	14 / 20 Passed

Description

87%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 provides explicit, natural 'Use when' triggers with concrete sources and a named standard. Minor room to add synonyms and file-extension references for fuller keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions and sources — 'changelog generation from commits, PRs, and releases following Keep a Changelog format' — but treats generation as a single action across sources rather than enumerating many distinct operations, leaving minor coverage gaps (e.g. no explicit version bumping).	4 / 5
Completeness	Clearly and explicitly answers both what ('Automate changelog generation from commits, PRs, and releases 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	Natural terms users would say are well covered — 'changelog generation', 'release workflows', 'release notes', 'commit conventions', 'commits, PRs, releases' — but a few common synonyms are missing (e.g. 'CHANGELOG.md', 'semantic versioning', 'version bump').	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Keep a Changelog, release notes, commit conventions) with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	18 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/changelog-automation/SKILL.md
Commit: 57c135b

Reviewed: 31 minutes 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.