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

58%

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

Quality

Content

46%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 well-structured and easy to navigate, but it reads more like an overview/marketing page than executable guidance: no git commands, no categorization logic, and no explicit validation checkpoint in the workflow. Some padding adds tokens without aiding execution.

Suggestions

Add concrete executable commands, e.g. `git log --since="last release" --no-merges` and a categorization mapping (feat/fix/breaking/security), so Claude can act rather than infer.

Insert an explicit validation/review step in the workflow (e.g. 'Verify categories and translate each entry to user-friendly language before outputting').

Trim marketing padding ('actually understand and appreciate', 'Inspired by', 'Related Use Cases') to reduce tokens without losing clarity.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with organized sections, but padded lines like 'that your customers and users will actually understand and appreciate' and non-essential sections ('Inspired by', 'Related Use Cases' duplicating 'When to Use') could be trimmed.	3 / 5
Actionability	Provides example user prompts and a sample output but no executable git commands (e.g. `git log --since`), no categorization rules, and no concrete procedure; guidance stays at the high-level 'What This Skill Does' conceptual list, missing the specific steps to execute.	2 / 5
Workflow Clarity	A rough six-step sequence is listed (scan, categorize, translate, format, filter, follow best practices) but checkpoints are absent or only implicit; the only validation hint is a Tips line 'Review and adjust the generated changelog before publishing'.	3 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and no bundle files to mismanage; the long inline example output and 'Related Use Cases' are minor content that could live elsewhere, keeping it just below a 5.	4 / 5
	Total	12 / 20 Passed

Description

70%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 concretely states what the skill does and is clearly distinguishable, but it lacks an explicit 'when to use' trigger clause, which caps its completeness. Some marketing padding ('Turns hours... into minutes') adds little.

Suggestions

Add an explicit trigger clause, e.g. 'Use when preparing release notes, product update summaries, or app store submission notes from git history.'

Drop the marketing sentence 'Turns hours of manual changelog writing into minutes of automated generation' in favor of trigger synonyms like 'what's new' or 'update notes'.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes') with only minor coverage gaps; the trailing 'Turns hours... into minutes' line is marketing fluff rather than a capability.	4 / 5
Completeness	The 'what' is clearly stated (creates user-facing changelogs from git commits) but there is no 'Use when...' clause or equivalent explicit trigger guidance; per the rubric a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('changelogs', 'git commits', 'release notes') but misses common synonyms like 'what's new' or 'update notes'; good but not comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (user-facing changelogs from git commits) with distinct triggers and minimal overlap risk versus related skills like commit-message generators.	5 / 5
	Total	16 / 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: MoizIbnYousaf/ai-agent-skills
Path: skills/changelog-generator/SKILL.md
Commit: 1159592

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