change-log-generator

Automatically generates change logs from git commits, patches, and pull requests. Use when preparing software releases, creating version summaries, or maintaining CHANGELOG.md files. Analyzes commit messages (including conventional commits), diff/patch files, and PR data to produce categorized Markdown change logs organized by type (Features, Bug Fixes, Breaking Changes, etc.). Ideal for release notes, version updates, and automated changelog maintenance.

1.15x

Quality

75%

Does it follow best practices?

Impact

95%

1.15x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/change-log-generator/SKILL.md

Quality

Content

50%

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

This skill provides highly actionable, executable guidance for changelog generation with comprehensive code examples and clear workflows. However, it suffers from severe verbosity - explaining basic concepts, including multiple template variations inline, and providing extensive Python code that could be referenced externally. The content would be significantly more effective at 1/3 the length with better use of progressive disclosure.

Suggestions

Move the Python parsing/categorization functions and CATEGORIES dictionary to a separate reference file (e.g., references/changelog_utils.py) and reference it

Consolidate the three template variations into a single recommended template inline, moving alternatives to references/templates.md

Remove explanations of conventional commit format basics - Claude knows this; keep only the parsing rules and edge cases

Add explicit validation checkpoints within the workflow (e.g., 'Verify parsed commits before categorization: check for empty descriptions, validate type mappings')

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~600+ lines, explaining concepts Claude already knows (what conventional commits are, basic git commands, Python regex patterns). The category mapping dictionaries, extensive templates, and multiple variations of the same information bloat the content significantly.	1 / 3
Actionability	The skill provides fully executable code examples throughout - complete Python functions for parsing commits, categorizing changes, and generating changelog entries. Git commands are copy-paste ready with multiple variations for different use cases.	3 / 3
Workflow Clarity	The 7-step workflow is clearly sequenced, but validation is limited to a checklist at the end rather than integrated checkpoints. There's no feedback loop for handling parsing errors or malformed commits during the process.	2 / 3
Progressive Disclosure	References to external files exist (references/conventional_commits.md, references/automation_examples.md) but the main document contains massive inline content that should be split out - the full Python functions, all three template variations, and the automation scripts could be separate reference files.	2 / 3
	Total	8 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that hits all the marks. It provides specific concrete actions, includes comprehensive natural trigger terms users would actually say, explicitly states both what the skill does and when to use it, and carves out a distinct niche that won't conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'generates change logs from git commits, patches, and pull requests', 'Analyzes commit messages (including conventional commits), diff/patch files, and PR data', 'produce categorized Markdown change logs organized by type (Features, Bug Fixes, Breaking Changes, etc.)'.	3 / 3
Completeness	Clearly answers both what ('generates change logs from git commits...produces categorized Markdown change logs') AND when ('Use when preparing software releases, creating version summaries, or maintaining CHANGELOG.md files').	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'change logs', 'git commits', 'patches', 'pull requests', 'releases', 'CHANGELOG.md', 'conventional commits', 'diff/patch files', 'PR data', 'release notes', 'version updates'.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on changelog generation from git/PR data with distinct triggers like 'CHANGELOG.md', 'release notes', 'conventional commits' - unlikely to conflict with general git or documentation skills.	3 / 3
	Total	12 / 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
skill_md_line_count	SKILL.md is long (779 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: ArabelaTso/Skills-4-SE
Commit: 0f00a4f

Reviewed: 4 months 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.