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.
76
64%
Does it follow best practices?
Impact
100%
1.25xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/documentation-generation/skills/changelog-automation/SKILL.mdCommitlint & 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%
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%
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%
47823e3
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.