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

76%

Does it follow best practices?

Impact

100%

1.25x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/documentation-generation/skills/changelog-automation/SKILL.md

The canonical home for this skill is changelog-automation in wshobson/agents

Quality

Content

65%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.

A comprehensive, highly actionable reference with executable configs for six toolchains, but it is verbose for a single SKILL.md and lacks both a sequenced workflow with validation checkpoints and progressive disclosure via reference files.

Suggestions

Move per-tool deep configs (semantic-release, git-cliff, commitizen) into separate reference files and keep only a concise Quick start plus pointers in SKILL.md to improve progressive disclosure and token efficiency.

Deduplicate the Conventional Commits type-to-section mapping, which currently appears in the table, the standard-version config, and the git-cliff parsers.

Add an explicit release workflow with validation checkpoints (e.g. dry-run, verify CHANGELOG, then publish) since releases and publishes are destructive batch operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code/config blocks with no basic-concept padding, but the Conventional Commits type-to-section mapping is repeated across three tools and six full tool configs are inlined, which could be tightened.	3 / 5
Actionability	It provides copy-paste-ready install commands, complete config files, and concrete commands (e.g. `git cliff -o CHANGELOG.md`, `cz bump --changelog`) covering the common cases across multiple ecosystems.	5 / 5
Workflow Clarity	The document presents six parallel method menus rather than a sequenced workflow, and the release/publish steps are batch/destructive operations with no explicit validation or verification checkpoints, capping this dimension at 3.	3 / 5
Progressive Disclosure	Section structure is good (When to Use, Core Concepts, Implementation, Templates, Best Practices, Resources), but all heavy reference material (per-tool configs, templates, examples) is inlined in SKILL.md with no reference files despite clear candidates for splitting.	3 / 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, third-person description that clearly states capabilities and provides explicit "Use when..." triggers tied to concrete scenarios. Minor keyword synonyms could be added, but it answers both what and when comprehensively.

Dimension	Reasoning	Score
Specificity	"Automate changelog generation from commits, PRs, and releases following Keep a Changelog format" names the domain plus several concrete actions, but coverage is not fully comprehensive (e.g., version bumping only implied).	4 / 5
Completeness	It 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	"setting up release workflows, generating release notes, or standardizing commit conventions" are natural user phrases, but a few synonyms (version bumps, semver, changelog) are missing.	4 / 5
Distinctiveness Conflict Risk	The Keep a Changelog / release-notes / commit-conventions niche is distinct with specific triggers, making overlap with other skills minimal.	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
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
Path: tests/ext_conformance/artifacts/agents-wshobson/documentation-generation/skills/changelog-automation/SKILL.md
Commit: 6453c0b

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