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/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 content is well-organized and self-contained with a clear structure and a useful example, but it leans descriptive rather than instructional: it lacks the concrete git commands that would make it fully actionable and offers no validation checkpoint for the generated output.

Suggestions

Include the concrete commands Claude should run to gather commits (e.g. `git log --since="<date>" --pretty=format:"..."`) so guidance is executable rather than descriptive.

Add a validation/review checkpoint step ("review the categorized entries; verify breaking changes and confirm noise was filtered before publishing").

Trim redundant sections ("Related Use Cases", "Inspired by", and the intro fluff) to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining concepts Claude already knows, but it carries redundant padding — "that your customers and users will actually understand and appreciate", the "Related Use Cases" list, and the "Inspired by" attribution — that could be trimmed.	2 / 3
Actionability	It provides example invocations and a concrete sample output, but as an instruction-only skill it omits the actual executable commands for retrieving commits (e.g. `git log --since=...`), leaving guidance incomplete.	2 / 3
Workflow Clarity	The six "What This Skill Does" items form a sequence, but they read as a feature list rather than an ordered workflow, and there are no validation or review checkpoints before publishing generated output.	2 / 3
Progressive Disclosure	A single self-contained file with clearly organized sections (When to Use, What This Skill Does, How to Use, Example, Tips) and no nested external references, so content is appropriately structured for a skill needing no bundle files.	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 distinct, clearly conveying what the skill does through concrete actions. Its main weakness is the missing explicit 'Use when...' trigger guidance, which limits both completeness and trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause listing natural triggers, e.g. "Use when generating release notes, changelogs, or app store update descriptions from git commits."

Broaden trigger term coverage with common variations users say ("release notes", "what's new", "version history", "update summary").

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 anchor for several specific concrete actions.	3 / 3
Completeness	Clearly states what the skill does, but there is no explicit 'Use when...' clause or equivalent trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms ("changelogs", "git commits", "release notes") but lacks an explicit trigger clause and common variations users would say, so it sits at 'some relevant keywords but missing common variations' rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (changelog generation from git commits) with distinct triggers that are unlikely to conflict with other skills.	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: Prat011/awesome-llm-skills
Path: changelog-generator/SKILL.md
Commit: 35e1ea2

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