skills.rest
sortie-ai
sortie-aiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

changelog-maintenance

Automate CHANGELOG.md entries following Keep a Changelog and Semantic Versioning.

121|10|Updated Mar 17, 2026
Search Tags:#changelog#versioning#documentation#release-management#semantic-versioning#keep-a-changelog
One-click install
npx skills add https://github.com/sortie-ai/sortie --skill changelog-maintenance-sortie-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-maintenance
Source: https://github.com/sortie-ai/sortie/tree/main/.github/skills/changelog-maintenance
Command: npx skills add https://github.com/sortie-ai/sortie --skill changelog-maintenance-sortie-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changelog maintenance is tedious and error-prone when coordinating multiple changes across releases. This Skill standardizes and automates the process, ensuring entries follow Keep a Changelog conventions and Semantic Versioning.

Core Features & Use Cases

  • Systematically create, format, and organize CHANGELOG.md entries for Unreleased and versioned releases.
  • Validate that entries answer the consumer-focused question of how the change affects installers, operators, and integrators.
  • Generate PR-numbered bullets and version links to maintain traceability across releases.

Quick Start

Update CHANGELOG.md with a new Unreleased entry for the latest release, following Keep a Changelog conventions and Semantic Versioning.

Frequently Asked Questions about changelog-maintenance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain a changelog for multiple pull requests before a release?▼

To maintain a changelog across multiple pull requests, this Skill automates organizing entries into an Unreleased section and tags bullets with PR numbers for traceability until versioning. It coordinates multi-PR changes systematically to prevent documentation drift.

What is the best way to format CHANGELOG.md entries using Keep a Changelog conventions?▼

Formatting CHANGELOG.md entries with Keep a Changelog conventions is automated by this Skill to ensure standardized categories and proper version links. It validates that entries explain how changes affect installers, operators, and integrators.

How does semantic versioning apply to unreleased changelog sections?▼

Semantic versioning applies to unreleased changelog sections by holding changes until a release triggers a version bump. This Skill ensures an Unreleased section exists, properly formats version headers, and migrates entries upon release.

Can I automate release documentation for feature fixes without manual formatting errors?▼

Automating release documentation for feature fixes is possible with this Skill, which standardizes entry creation and prevents formatting errors. It populates categories systematically and generates PR-numbered bullets to maintain traceability.

When do I need to validate changelog entries for operators and integrators?▼

You need to validate changelog entries for operators and integrators during release preparation to ensure documentation answers consumer-focused questions. This Skill checks that changes clearly explain their impact on installers and integrators before release.

Related Skills

Explore More Content & Communication Skills→
k97k97
4

gen-release-notes

Generate structured release notes from git commit history and pull request data.

Community
Advanced
vsokhvsokh

release

Assess release readiness and generate versioned changelogs from git history.

Community
Advanced
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
maslennikov-igmaslennikov-ig
243

generate-changelog

Generate Keep a Changelog–compliant Markdown sections from git commits, plan files, or manual entries.

Community
Advanced