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

66%

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

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-sectioned but severely lacking in actionability: instructions are abstract directives with no tools, commands, or examples, and the sole external reference (resources/implementation-playbook.md) points to a file that is missing from the bundle. The skill reads as a placeholder overview rather than executable guidance.

Suggestions

Replace abstract instruction bullets with concrete guidance: name specific tools (e.g., git-cliff, semantic-release, conventional-changelog) with example commands or configuration snippets for each step.

Create the referenced resources/implementation-playbook.md file (or remove the reference) so the bundle's only external pointer resolves; include Keep a Changelog section templates and example commit-convention configs there.

Add an explicit validation checkpoint with a feedback loop, e.g., 'Generate a dry-run changelog, diff against the previous release notes, fix gaps or wording, then publish' — currently the review step has no retry guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept over-explanation ("Select a changelog format and versioning strategy.") and assumes Claude's competence. Not 5 because the generic boilerplate in the Limitations and Safety sections ("Do not treat the output as a substitute for environment-specific validation...") is padding that could be trimmed.	4 / 5
Actionability	The Instructions are high-level hints only — "Enforce commit conventions or labeling rules", "Configure tooling to generate and publish notes" — with no named tools, commands, examples, or Keep a Changelog section structure, matching 'minimal concrete guidance; high-level hints but missing the specific steps'. Not 3 because there is no concrete executable detail anywhere; not 1 because a rough actionable sequence is described rather than pure description.	2 / 5
Workflow Clarity	A sequence is present (select format → enforce conventions → configure tooling → review output) and "Review output for accuracy, completeness, and wording" acts as a checkpoint, but steps are poorly defined with no commands and no error-recovery guidance, matching 'steps listed but validation gaps; checkpoints implicit'. Not 4 because the steps lack concrete commands and the review checkpoint has no feedback loop.	3 / 5
Progressive Disclosure	Sections are well-organized and the reference is clearly signaled twice ("If detailed examples are required, open `resources/implementation-playbook.md`"), but the referenced file does not exist in the bundle — the one-level-deep reference dangles, so navigation leads nowhere. This falls between 'references present but not clearly signaled' and the well-structured anchor 4; the broken reference caps it at 3.	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 is strong: it explicitly states both what the skill does and when to use it, with natural trigger phrases and a distinct niche. Minor improvements are possible by adding common synonyms (version history, CHANGELOG.md, semantic versioning) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete actions — "Automate changelog generation from commits, PRs, and releases", "generating release notes", "standardizing commit conventions" — matching the 'several specific actions; minor gaps' anchor. Not 5 because coverage gaps remain (e.g., semantic versioning management is absent); not 3 since more than 1-2 actions are explicitly listed.	4 / 5
Completeness	Clearly answers both: what it does ("Automate changelog generation from commits, PRs, and releases following Keep a Changelog format") and when to use it ("Use when setting up release workflows, generating release notes, or standardizing commit conventions") with concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Includes natural user phrases like "changelog", "commits", "PRs", "release notes", "release workflows", and "commit conventions" — good keyword coverage. Not 5 because common synonyms and variations such as "version history", "CHANGELOG.md", or "semantic versioning" are missing.	4 / 5
Distinctiveness Conflict Risk	A clear niche (changelog/release-note automation) with distinct trigger terms minimizes conflict risk. Not 5 because there is minor overlap potential with generic git-workflow or release-automation skills; not 3 because the Keep a Changelog framing and commit-convention triggers are fairly distinctive.	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/agentic-awesome-skills
Path: skills/changelog-automation/SKILL.md
Commit: 7b534bc

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