Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
Install with Tessl CLI
npx tessl i github:wshobson/agents --skill changelog-automation79
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/skillAgent success when using this skill
Validation for skill structure
Commitlint & husky configuration
Extends config-conventional
100%
100%
All 11 type-enum values
0%
100%
subject-case: no start-case
0%
100%
subject-case: no pascal-case
0%
100%
subject-case: no upper-case
0%
100%
subject-max-length 72
0%
100%
Husky hook content
100%
100%
Husky init command
0%
100%
@commitlint/cli dependency
100%
100%
@commitlint/config-conventional dependency
100%
100%
Without context: $0.1966 · 39s · 11 turns · 12 in / 1,994 out tokens
With context: $0.5320 · 1m 27s · 24 turns · 394 in / 5,243 out tokens
Keep a Changelog format
Changelog header
100%
100%
Keep a Changelog link
100%
100%
Unreleased section
100%
100%
Version-date format
100%
100%
feat commits in Added
100%
100%
fix commits in Fixed
100%
100%
refactor/perf in Changed
100%
100%
docs/chore excluded
0%
100%
Major version for breaking change
100%
100%
Footer comparison links
100%
100%
Without context: $0.1996 · 42s · 8 turns · 9 in / 2,791 out tokens
With context: $0.4456 · 1m 41s · 15 turns · 14 in / 5,521 out tokens
standard-version release configuration
feat → Features
100%
100%
fix → Bug Fixes
100%
100%
perf → Performance Improvements
100%
100%
revert → Reverts
100%
100%
docs hidden
100%
100%
style hidden
100%
100%
chore hidden
100%
100%
refactor hidden
100%
100%
commitUrlFormat template
62%
100%
compareUrlFormat template
87%
100%
release:dry script
50%
100%
release:patch, :minor, :major scripts
100%
100%
Without context: $0.5648 · 2m 21s · 27 turns · 27 in / 6,085 out tokens
With context: $0.5619 · 1m 30s · 23 turns · 422 in / 5,205 out tokens
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.