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.
82
75%
Does it follow best practices?
Impact
95%
1.15xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/change-log-generator/SKILL.mdBreaking change priority and category ordering
Breaking changes first
100%
100%
Breaking change warning emoji
0%
100%
No duplicate breaking change
0%
0%
Category order: feat before fix
100%
100%
Category order: fix before perf
100%
100%
Bold scope formatting
100%
100%
SHA truncated to 7 chars
0%
100%
Commit SHA links
0%
100%
Version header format
100%
100%
Present tense descriptions
57%
100%
Non-conventional commit categorization and issue extraction
add/implement/create → Features
100%
100%
fix/resolve/correct/patch → Bug Fixes
100%
100%
update/improve/enhance → Refactoring
100%
83%
doc/readme/comment → Documentation
100%
100%
Unmatched commits in other
100%
100%
Merge commits excluded
100%
100%
Issue references extracted
100%
100%
Issue reference patterns
100%
100%
Present tense descriptions
100%
100%
Version header format
100%
100%
Changelog update with contributors, comparison links, and migration guides
New entry prepended
100%
100%
Keep a Changelog header preserved
100%
100%
Semver version header
100%
100%
Full Changelog comparison link
100%
100%
Contributors section
100%
100%
Migration guide for breaking change
100%
100%
Breaking changes section first
100%
100%
Bold scope formatting
100%
100%
Category order maintained
100%
100%
Existing entries intact
100%
100%
Changelog commit message
0%
100%
0f00a4f
Table of Contents
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.