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.25x

Quality

—

Does it follow best practices?

Impact

100%

1.25x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable with complete, executable configs across many tools, but presented as a long monolithic document of parallel alternatives rather than a guided, validated workflow. Splitting methods and templates into reference files and adding a recommended default path would improve it.

Suggestions

Promote one default method as the primary workflow and move the other five tool configs into separate reference files (e.g. references/semantic-release.md), reducing the inline volume.

Add a short sequenced setup workflow with explicit validation checkpoints (e.g. verify commitlint blocks bad messages, dry-run standard-version/semantic-release before publishing) rather than only listing parallel alternatives.

Move the release-note templates and commit-message examples into references/ to keep SKILL.md as a lean overview pointing one level deep.

Dimension	Reasoning	Score
Conciseness	Content is actionable rather than padded with concepts Claude knows, but six full alternative method configs plus templates and examples (~580 lines) is more than a single path requires and could be tightened or split out.	2 / 3
Actionability	Provides real, copy-paste-ready configurations and commands across tools — npm/npx, semantic-release config, GitHub Actions YAML, git-cliff TOML, and commitizen — matching the fully executable anchor.	3 / 3
Workflow Clarity	Methods are presented as parallel alternatives (Method 1–6) rather than a sequenced workflow, with no validation or verification checkpoints for the setup operations, matching the 'steps present but checkpoints missing' anchor.	2 / 3
Progressive Disclosure	No bundle files exist, and all reference material (six method configs, release-note templates, examples) is inline in one monolithic SKILL.md; sections organize it but content that should be separate is not split out.	2 / 3
	Total	9 / 12 Passed

Description

100%

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, concise description that states concrete capabilities, uses natural trigger terms, and explicitly pairs 'what' with 'when' in third person. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'changelog generation from commits, PRs, and releases following Keep a Changelog format' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ('Automate changelog generation...') and when ('Use when setting up release workflows, generating release notes, or standardizing commit conventions').	3 / 3
Trigger Term Quality	Natural user-facing terms appear: 'release workflows', 'release notes', 'commit conventions', plus 'commits, PRs, and releases' — good coverage of phrases users would actually say.	3 / 3
Distinctiveness Conflict Risk	Clear niche — changelog/release-note automation tied to Keep a Changelog and commit conventions — with distinct triggers unlikely to overlap with unrelated skills.	3 / 3
	Total	12 / 12 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
skill_md_line_count	SKILL.md is long (581 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Commit: e9f9b67

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