CtrlK
BlogDocsLog inGet started
Tessl Logo

changelog-maintenance

Maintain a clear and informative changelog for software releases. Use when documenting version changes, tracking features, or communicating updates to users. Handles semantic versioning, changelog formats, and release notes.

83

1.02x
Quality

77%

Does it follow best practices?

Impact

94%

1.02x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent-skills/changelog-maintenance/SKILL.md
SKILL.md
Quality
Evals
Security

Evaluation results

100%

4%

Create a Project Changelog

Changelog format and structure

Criteria
Without context
With context

Standard header text

50%

100%

Keep a Changelog reference

100%

100%

Semantic Versioning reference

100%

100%

Unreleased section

100%

100%

ISO 8601 date format

100%

100%

Change categories used

100%

100%

Reverse chronological order

100%

100%

Comparison links present

100%

100%

Unreleased comparison link

100%

100%

No vague entries

100%

100%

User perspective writing

100%

100%

Multiple versions present

100%

100%

100%

Prepare Release Documentation for v2.5

Release notes and output structure

Criteria
Without context
With context

Correct MINOR version bump

100%

100%

CHANGELOG.md produced

100%

100%

RELEASES.md produced

100%

100%

Release notes What's New section

100%

100%

Release notes Improvements section

100%

100%

Release notes Bug Fixes section

100%

100%

Full changelog link

100%

100%

Changelog category sections

100%

100%

ISO 8601 date in changelog

100%

100%

No vague changelog entries

100%

100%

Comparison links in changelog

100%

100%

Unreleased section present

100%

100%

82%

Document a Major API Redesign

Breaking changes migration guide

Criteria
Without context
With context

MAJOR version bump

100%

100%

Migration guide file location

100%

100%

Migration guide filename

100%

100%

Before/after code examples — auth

100%

100%

Before/after code examples — response format

100%

100%

Deprecation timeline

0%

0%

CHANGELOG.md MAJOR entry

100%

100%

Deprecated section in changelog

25%

0%

Migration guide link in changelog

75%

100%

Breaking changes in release notes

100%

100%

ISO 8601 date and correct version

100%

100%

Repository
supercent-io/skills-template
Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

Table of Contents

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.