skills.rest
LucasBiason
LucasBiasonCOMMUNITY
Explore all skills by this author →
GitHub

changelog-management

Enforce Keep a Changelog format and Semantic Versioning for CHANGELOG entries.

Updated Aug 27, 2026
Search Tags:#git#changelog#versioning#documentation#release-management#semantic-versioning#keep-a-changelog
One-click install
npx skills add https://github.com/LucasBiason/cursor-multiagent-system --skill changelog-management-lucasbiason
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-management
Source: https://github.com/LucasBiason/cursor-multiagent-system/tree/main/skills/workflow/changelog
Command: npx skills add https://github.com/LucasBiason/cursor-multiagent-system --skill changelog-management-lucasbiason

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Este skill garante que todos os projetos mantenham CHANGELOGs atualizados e versionados, alinhando-se ao Keep a Changelog e ao Semantic Versioning para evitar ambiguidades de release.

Core Features & Use Cases

  • Obrigatoriedade de CHANGELOG.md na raiz de todo projeto, seguindo o formato Keep a Changelog.
  • Orientação para uso de Semantic Versioning com marcação de seções Unreleased e mudanças por categoria (Added, Changed, Fixed, etc).
  • Uso recomendado durante criação, commits, releases e documentação para manter um histórico claro de alterações.
  • Cenário de uso: ao preparar uma release, o skill orienta a registrar mudanças essenciais e gerar notas de versão consistentes.

Quick Start

Execute a CHANGELOG validation at the repository root to ensure CHANGELOG.md exists and follows Keep a Changelog. Update the Unreleased section with new changes and ensure entries are categorized correctly (Added, Changed, Fixed, etc.). Prepare a release by creating a proper tag and updating version references after documenting changes.

Frequently Asked Questions about changelog-management

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

FAQPage Schema
How do I maintain an accurate changelog using Keep a Changelog format?▼

To maintain an accurate changelog, keep a CHANGELOG.md file at your repository root and structure entries into Added, Changed, and Fixed categories following the Keep a Changelog format. This ensures changes are tracked consistently across project lifecycles.

What is the best way to handle Unreleased sections and Semantic Versioning for a release?▼

Handling Unreleased sections involves documenting new changes categorized by type before promoting them to a tagged version. Semantic Versioning dictates the version bump, ensuring release notes align with the actual codebase modifications.

How do I prepare a release with proper versioning and changelog updates?▼

To prepare a release, update the Unreleased section with categorized changes, create a proper version tag using Semantic Versioning rules, and update version references in documentation to generate consistent version notes.

Do I need a CHANGELOG.md file at the repository root for every project?▼

Yes, a CHANGELOG.md file at the repository root is mandatory. It enforces versioning and tracks changes across creation, commits, and releases, preventing release ambiguities by following the Keep a Changelog standard.

Why does Semantic Versioning require categorized changelog entries?▼

Semantic Versioning requires categorized changelog entries to clarify the impact of changes. Grouping updates into Added, Changed, or Fixed sections directly informs whether a major, minor, or patch version bump is necessary.

Can I use Keep a Changelog for both commit and release documentation?▼

Yes, Keep a Changelog is recommended during both commits and releases. It maintains a clear history of alterations by enforcing categorized Unreleased entries that seamlessly transition into official release notes.

Related Skills

Explore More Software Engineering Skills→
kmylpenterkmylpenter

np

Initialize a new project directory with a standardized KFG structure and Git setup.

Community
Intermediate
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
aaron-vazaaron-vaz
1

conventional-commits

Validate Git commit messages against the Conventional Commits specification.

Community
Intermediate
RussianLioNRussianLioN
1

generate-changelog

Generate Keep a Changelog entries from git commits, plan files, or manual data.

Community
Intermediate