changelog-bump-ver

Organize changelog entries and increment Maven project versions for releases.

1|Updated Feb 14, 2026

Search Tags:#automation #changelog #versioning #release #maven

Ready to run

npx skills add https://github.com/mir-am/skills-agents-ai-coding --skill changelog-bump-ver

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-bump-ver
Source: https://github.com/mir-am/skills-agents-ai-coding/tree/main/skills/changelog-bump-ver
Command: npx skills add https://github.com/mir-am/skills-agents-ai-coding --skill changelog-bump-ver

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of moving unreleased changelog entries into a new versioned release section and updates project version numbers in Maven files, simplifying release management.

Core Features & Use Cases

Promotes the ## [Unreleased] entries in CHANGELOG.md into a new release section with the appropriate version and date.
Adds a fresh ## [Unreleased] section for future development.
Updates Maven pom.xml files' <project><version> elements to the next snapshot version based on the release version.
Ideal for build automation and continuous deployment pipelines to maintain consistent release logs and versioning.

Quick Start

Run this skill in your repository to convert the current unreleased changes into a new release, update the changelog, and synchronize Maven project versions automatically.

Frequently Asked Questions about changelog-bump-ver

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

FAQPage Schema

How do I automate updating a changelog and Maven version for a release?▼

Automate release preparation by promoting unreleased changelog entries into a versioned section and updating Maven pom.xml files. This skill organizes release notes and increments project versions simultaneously for consistent deployment workflows.

What is the process for moving unreleased changelog entries into a new release section?▼

The process converts the current Unreleased section into a dated, versioned release block, then generates a new Unreleased section for future changes. This maintains a continuous changelog history across release cycles.

Do I need an existing CHANGELOG.md and pom.xml to use this versioning automation?▼

Yes, this automation requires an existing CHANGELOG.md with an Unreleased section and Maven pom.xml files. It parses these specific file structures to correctly update version numbers and organize release notes.

How does Maven version incrementing work when preparing a new release?▼

Maven version incrementing updates the project version elements in pom.xml files to the next snapshot version based on the release version. This advances the project to the next development cycle after a release.

Can I use this to maintain semantic versioning standards in continuous deployment pipelines?▼

Yes, this automation is ideal for continuous deployment pipelines to maintain consistent release logs and versioning. It organizes changelog entries and updates Maven versions while adhering to semantic versioning standards.

Why is my changelog bump not working without an unreleased section?▼

Changelog bumping requires an existing Unreleased section in CHANGELOG.md to function correctly. Without this section, the automation has no entries to promote into a new versioned release section.