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

38%

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

Quality

Content

35%

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

This skill reads more like a product description than actionable instructions for Claude. It explains what the skill does conceptually but fails to provide the concrete implementation details - no git commands, no parsing logic, no code for categorizing commits or transforming technical language. The example output is helpful but there's no guidance on how to actually produce it.

Suggestions

Add executable code showing how to extract git commits (e.g., `git log --oneline --since='7 days ago'`) and parse them programmatically

Include concrete rules or patterns for categorizing commits (e.g., 'commits starting with feat: → New Features, fix: → Bug Fixes')

Provide specific transformation examples showing input commit messages and their user-friendly outputs

Add validation steps for edge cases: repositories without tags, non-conventional commit messages, or empty date ranges

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary explanation (e.g., 'that your customers and users will actually understand and appreciate') and the 'What This Skill Does' section explains concepts Claude already understands. The 'When to Use This Skill' list is overly extensive for what is a straightforward task.	2 / 3
Actionability	The skill provides no executable code or concrete commands - only natural language prompts like 'Create a changelog from commits since last release'. There are no actual git commands, scripts, or code snippets showing how to extract commits, parse them, or format output.	1 / 3
Workflow Clarity	The numbered list in 'What This Skill Does' describes the conceptual workflow but lacks explicit validation steps or error handling. There's no guidance on what to do if git history is malformed, commits don't follow conventions, or the repository has no tags.	2 / 3
Progressive Disclosure	The content is reasonably structured with clear sections, but references external files (CHANGELOG_STYLE.md) without explaining what should be in them. The 'Related Use Cases' section adds little value and could be trimmed or moved to a separate file.	2 / 3
	Total	7 / 12 Passed

Description

42%

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 excels at explaining specific capabilities with concrete actions like analyzing commits and categorizing changes. However, it critically lacks any 'Use when...' clause or explicit trigger guidance, which is essential for Claude to know when to select this skill. The marketing-style closing sentence ('Turns hours...into minutes') adds no selection value.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks for changelogs, release notes, version summaries, or wants to document changes between releases'

Include common file/format variations users might mention: 'CHANGELOG.md', 'release notes', 'what's new section', 'version history'

Remove the marketing fluff ('Turns hours of manual changelog writing into minutes') and replace with actionable trigger terms

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'analyzing commit history', 'categorizing changes', 'transforming technical commits into clear, customer-friendly release notes'. These are concrete, actionable capabilities.	3 / 3
Completeness	Clearly describes WHAT the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no trigger guidance at all.	1 / 3
Trigger Term Quality	Contains relevant keywords like 'changelogs', 'git commits', 'release notes', but missing common variations users might say like 'CHANGELOG.md', 'version notes', 'what's new', or 'release documentation'.	2 / 3
Distinctiveness Conflict Risk	Reasonably specific to changelog generation from git, but could overlap with general git analysis skills or documentation generation skills. The focus on 'user-facing' and 'customer-friendly' helps distinguish it somewhat.	2 / 3
	Total	8 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ComposioHQ/awesome-claude-skills
Path: changelog-generator/SKILL.md
Commit: 2790447

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.