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

66%

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/skills/changelog-automation/SKILL.md

The canonical home for this skill is changelog-automation in rmyndharis/antigravity-skills

Quality

Content

50%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-structured but provides only abstract guidance with no concrete tooling or commands, no validation checkpoints, and a broken reference to a missing playbook file. These gaps leave the workflow more of an outline than an executable procedure.

Suggestions

Name specific tools and give a concrete config or command example (e.g. conventional-changelog / semantic-release with a sample release.config.js) instead of "Configure tooling to generate and publish notes."

Add a validation/checklist step in the workflow — e.g. verify the generated changelog matches the Keep a Changelog format and that no secrets/internal details leaked before publishing — with a fix-and-retry loop.

Create the referenced `resources/implementation-playbook.md` (or point the reference at an existing bundle path under references/) so the promised detailed patterns and templates are actually reachable.

Dimension	Reasoning	Score
Conciseness	The body is lean with terse bullet instructions and no over-explanation of concepts Claude already knows; only the opening sentence mildly restates the description and could be trimmed.	4 / 5
Actionability	Instructions are high-level hints ("Configure tooling to generate and publish notes", "Enforce commit conventions or labeling rules") with no named tools (e.g. semantic-release, commitizen), commands, or config examples, missing the specific steps to execute.	2 / 5
Workflow Clarity	A four-step sequence is present (select format, enforce conventions, configure tooling, review output) but it lacks validation/feedback checkpoints for a publishing/batch operation, which caps it at 3 per the rubric guideline.	3 / 5
Progressive Disclosure	Sections are well-organized and the playbook reference is one level deep and clearly signaled, but the referenced `resources/implementation-playbook.md` does not exist in the bundle (no references/scripts/assets directories), so navigation dead-ends.	3 / 5
	Total	12 / 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.

The description cleanly answers both what the skill does and when to use it, with natural trigger terms and a clear niche. It is held back from full marks only by somewhat single-action specificity and a few missing synonyms.

Dimension	Reasoning	Score
Specificity	Names the changelog domain plus concrete sources ("commits, PRs, and releases") and a specific format ("Keep a Changelog"), but centers on one core action (generation) with source variants rather than multiple distinct actions, so it falls just below comprehensive.	4 / 5
Completeness	Explicitly states both the what ("Automate changelog generation from commits, PRs, and releases following Keep a Changelog format") and the when ("Use when setting up release workflows, generating release notes, or standardizing commit conventions") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"setting up release workflows, generating release notes, or standardizing commit conventions" are natural phrases users would say, but common synonyms/extensions like CHANGELOG.md, semver, and version bump are absent.	4 / 5
Distinctiveness Conflict Risk	Changelog/release-notes is a clear niche with distinct triggers, but there is minor overlap risk with general release-tooling or git-workflow 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/changelog-automation/SKILL.md
Commit: 57c135b

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.