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.
86
71%
Does it follow best practices?
Impact
97%
1.16xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/documentation-generation/skills/changelog-automation/SKILL.mdCommitlint & husky configuration
Extends config-conventional
100%
100%
All 11 type-enum values
100%
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
100%
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
50%
62%
compareUrlFormat template
62%
100%
release:dry script
0%
100%
release:patch, :minor, :major scripts
100%
100%
semantic-release full automation config
main branch configured
100%
100%
beta pre-release branch
100%
100%
alpha pre-release branch
100%
100%
commit-analyzer plugin
100%
100%
release-notes-generator plugin
100%
100%
changelog plugin present
100%
100%
changelog file setting
100%
100%
npm plugin present
100%
100%
npmPublish true
100%
100%
github plugin present
100%
100%
github dist assets
0%
100%
git plugin present
100%
100%
git plugin assets
100%
100%
git plugin skip ci
100%
100%
plugin order
100%
100%
GitHub Actions release workflow
push to main trigger
100%
100%
workflow_dispatch trigger
100%
100%
release_type input
100%
100%
contents: write permission
100%
100%
pull-requests: write permission
0%
0%
fetch-depth: 0
100%
100%
actions/checkout@v4
100%
100%
actions/setup-node@v4
100%
100%
node-version: 20
0%
100%
git user.name github-actions[bot]
100%
100%
git user.email noreply address
100%
100%
push with follow-tags
100%
100%
git-cliff changelog configuration
conventional_commits = true
100%
100%
filter_unconventional = true
100%
100%
tag_pattern v[0-9]*
100%
100%
sort_commits oldest
100%
100%
feat → Features
100%
100%
fix → Bug Fixes
100%
100%
perf → Performance
100%
80%
refactor → Refactoring
100%
100%
chore(release) skipped
40%
100%
Tera group_by in body template
100%
100%
generate to file command
100%
100%
range generation command
70%
100%
dry-run preview command
42%
100%
91fe43e
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.