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

78%

Does it follow best practices?

Impact

95%

1.15x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

67%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.

Highly actionable with executable code and a clear sequenced workflow, but the body is verbose and monolithic: it over-explains conventional commits and inlines template/script content that should live in the (currently missing) reference files.

Suggestions

Create the referenced files (conventional_commits.md, keep_a_changelog.md, automation_examples.md) and move the full conventional-commit type list, the three template variants, and the bash automation script into them, keeping SKILL.md as a lean overview.

Trim the conventional-commit format explanation and type list — Claude already knows this — to a brief pointer plus edge cases only.

Add an explicit validate→fix→retry loop around the CHANGELOG.md prepend/release-publish step so failed validation checkpoints feed back into correction.

Dimension	Reasoning	Score
Conciseness	The body is ~775 lines with three full template variants, a complete bash automation script, and an explanation of conventional-commit types that Claude already knows; mostly actionable code but noticeably over-long and could be tightened by moving detail to references.	3 / 5
Actionability	Abundant copy-paste-ready executable guidance — concrete git/gh commands, complete Python parsing/categorization/formatting functions, and ready-to-use Markdown templates covering the common release-note cases.	5 / 5
Workflow Clarity	Seven clearly sequenced steps with a validation checklist in Step 7, but no explicit validate→fix→retry feedback loop for the batch commit processing and CHANGELOG.md overwrite, leaving a minor checkpoint gap.	4 / 5
Progressive Disclosure	References are signaled ('See references/conventional_commits.md', 'keep_a_changelog.md', 'automation_examples.md') but those files do not exist, while large amounts of content that belongs in them — conventional-commit detail, three full templates, automation scripts — are inlined in the monolithic body.	2 / 5
	Total	14 / 20 Passed

Description

88%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.

A strong, third-person description that clearly states what the skill does and when to invoke it, with concrete actions and natural trigger phrases. It is mostly distinct from neighboring skills with only minor overlap risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'generates change logs from git commits, patches, and pull requests' and 'Analyzes commit messages... diff/patch files, and PR data to produce categorized Markdown change logs organized by type' — covering inputs, processing, and output comprehensively.	5 / 5
Completeness	Explicitly answers both what ('Automatically generates change logs... produce categorized Markdown change logs') and when ('Use when preparing software releases, creating version summaries, or maintaining CHANGELOG.md files... Ideal for release notes') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural trigger coverage ('preparing software releases', 'version summaries', 'maintaining CHANGELOG.md files', 'release notes', 'version updates') but a few common synonyms (e.g. 'git history', 'release notes' variants) are absent, stopping short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Has a clear niche (changelog generation from git/PRs) with distinct triggers, but could see minor overlap with adjacent skills such as commit-message writing or general git helpers.	4 / 5
	Total	18 / 20 Passed

Validation

81%

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 — 13 / 16 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
relative_links	Relative link issues: 44 missing	Warning
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	13 / 16 Passed

Repository: ArabelaTso/Skills-4-SE
Path: skills/change-log-generator/SKILL.md
Commit: 4f38503

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