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.

Install with Tessl CLI

npx tessl i github:Lingjie-chen/MT5 --skill changelog-generator

What are skills?

Review — 45%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

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 effectively communicates specific capabilities for changelog generation with good technical detail. However, it lacks explicit trigger guidance ('Use when...') which is critical for skill selection, and could benefit from additional natural trigger terms users might employ when requesting this functionality.

Suggestions

Add a 'Use when...' clause with trigger terms like 'changelog', 'release notes', 'what changed', 'version history', 'CHANGELOG.md'

Include common file format variations users might mention: 'CHANGELOG.md', 'HISTORY.md', 'release documentation'

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 answers 'what does this do' with detailed capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied through the description of the task.	2 / 3
Trigger Term Quality	Contains relevant keywords like 'changelogs', 'git commits', 'release notes', but missing common variations users might say such as 'CHANGELOG.md', 'version notes', 'what's new', or 'release documentation'.	2 / 3
Distinctiveness Conflict Risk	Clear niche combining git commits with changelog/release notes generation. Distinct from general git skills or documentation skills due to the specific transformation from commits to customer-facing content.	3 / 3
	Total	10 / 12 Passed

Implementation

22%

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 or feature overview than actionable instructions for Claude. It explains what a changelog generator should do conceptually but provides no executable code, git commands, or concrete implementation steps. The example shows desired output but not how to achieve it.

Suggestions

Add executable git commands for extracting commit history (e.g., `git log --since='7 days ago' --pretty=format:'%s|%b|%h'`)

Include a concrete workflow with actual steps: 1) Run git log command, 2) Parse output, 3) Categorize by commit prefix, 4) Transform to user-friendly language, 5) Format output

Provide code or regex patterns for categorizing commits (e.g., commits starting with 'feat:', 'fix:', 'chore:')

Remove the 'When to Use This Skill' section entirely - Claude doesn't need to be told when changelogs are useful

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. It only shows natural language prompts ('Create a changelog from commits since last release') without any actual git commands, scripts, or implementation details Claude would need to execute this task.	1 / 3
Workflow Clarity	The 'What This Skill Does' section lists conceptual steps but provides no actual workflow for execution. There are no validation checkpoints, no error handling, and no concrete sequence of git commands or processing steps to follow.	1 / 3
Progressive Disclosure	The content is reasonably organized with clear sections, but it's somewhat monolithic with no references to external files for detailed implementation. The structure is adequate but could benefit from separating the example output format into a reference file.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

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