changelog-generator

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Quality

62%

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

Quality

Content

57%

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

The body is well-structured and appropriately scoped to one file, but it is padded and gives only high-level process description rather than executable, rule-based guidance with verification steps. Tightening the prose and adding concrete git commands plus a categorization rubric would lift the weaker dimensions.

Suggestions

Add the concrete git command(s) to source commits (e.g. `git log v2.4.0..HEAD --no-merges`) instead of only describing scanning in prose.

Provide an explicit categorization rubric mapping commit prefixes/types to changelog categories (features, improvements, fixes, breaking, security) rather than just naming the categories.

Trim "What This Skill Does" and "Related Use Cases" to remove content already covered by the description or inferable by Claude, and add a verify step to review filtered output before publishing.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but padded: "What This Skill Does" restates capabilities already in the description, and "Tips"/"Related Use Cases" add content Claude can infer, matching the score-2 anchor for mostly efficient with some unnecessary explanation.	2 / 3
Actionability	Concrete example invocations and a full example output give some executable guidance, but there is no git-log command, categorization rule set, or transformation guidance — key details are missing, matching the score-2 anchor for some concrete guidance but incomplete.	2 / 3
Workflow Clarity	Steps are listed (scan, categorize, translate, format, filter) as a feature list rather than an ordered procedure, and there are no validation checkpoints for a batch generation task, which per the scoring notes caps workflow clarity at 2.	2 / 3
Progressive Disclosure	A single well-organized file under 50 lines with clear sections and no need for external references, which per the simple-skills note merits a 3.	3 / 3
	Total	9 / 12 Passed

Description

67%

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 specific and distinctive about what it does, but omits any explicit "when to use it" trigger guidance, which caps completeness and trigger-term quality. Adding a Use-when clause listing natural user phrasings would lift the two weaker dimensions.

Suggestions

Append an explicit trigger clause such as "Use when preparing release notes, changelogs, app store update descriptions, or product update summaries from git history."

Broaden natural trigger terms to include phrasings users actually say, e.g. "release notes", "what's new", "version updates", "shipping notes".

Keep the concrete action list but drop the marketing line about "hours... into minutes", which adds no capability information.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes" — matching the score-3 anchor for multiple specific concrete actions.	3 / 3
Completeness	It clearly states what the skill does but never says when to use it; per the judging guidelines a missing explicit trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Relevant natural terms appear (git commits, changelogs, release notes) but common variations users would say are missing and there is no explicit "Use when..." trigger clause, matching the score-2 anchor for some relevant keywords but missing common variations.	2 / 3
Distinctiveness Conflict Risk	It carves a clear niche (user-facing changelogs from git commits) with distinct triggers unlikely to overlap with other skills, matching the score-3 anchor.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: composio-community/awesome-claude-plugins
Path: changelog-generator/skills/changelog-generator/SKILL.md
Commit: e521f7a

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