semver-changelog

Compare HEAD with the latest SemVer tag and update CHANGELOG.md using Keep a Changelog structure.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/prulloac/git-blame-vsc --skill semver-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: semver-changelog
Source: https://github.com/prulloac/git-blame-vsc/tree/main/.agents/skills/semver-changelog
Command: npx skills add https://github.com/prulloac/git-blame-vsc --skill semver-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manual maintenance of CHANGELOG.md is error-prone and often out-of-date, making it hard for teams to track releases and communicate changes effectively.

Core Features & Use Cases

  • Identify Latest Released Tag: Find the most recent Semantic Versioning (SemVer) tag to anchor the changelog history.
  • Analyze Changes: Compare HEAD with the latest tag to surface Added, Changed, Deprecated, Removed, Fixed, and Security changes.
  • Update or Initialize CHANGELOG.md: Generate or update a CHANGELOG.md in Keep a Changelog format, creating an Unreleased section when appropriate.
  • Compliance & Clarity: Adheres to Keep a Changelog structure and SemVer rules, with clear categorization and versioned history.

Quick Start

Identify the latest SemVer tag and update CHANGELOG.md following Keep a Changelog formatting rules.

Frequently Asked Questions about semver-changelog

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

FAQPage Schema
How do I automate changelog generation from git tags using semantic versioning?

Automate changelog generation by identifying the latest SemVer tag, comparing it with HEAD, categorizing changes into Added, Changed, Deprecated, Removed, Fixed, and Security, and updating CHANGELOG.md following Keep a Changelog structure.

What is the Keep a Changelog format for organizing version history?

Keep a Changelog is a standardized format that organizes version history into clear categories like Added, Changed, Fixed, and Security, maintaining an Unreleased section for pending updates and adhering to SemVer guidelines.

How do I categorize git commits into Added, Changed, and Fixed sections for a release?

Categorize git commits by comparing HEAD with the latest released tag, then sorting changes into Added, Changed, Deprecated, Removed, Fixed, and Security sections to produce a compliant CHANGELOG.md file.

Can I generate a CHANGELOG.md from existing git history without manual entry?

Yes, generate or update CHANGELOG.md automatically by analyzing the diff between HEAD and the latest SemVer tag, categorizing the changes, and writing them into Keep a Changelog format in the repository root.

Does this changelog automation work if my repository has no previous CHANGELOG.md?

Yes, it initializes a new CHANGELOG.md in the repository root using Keep a Changelog structure, creating an Unreleased section if needed and anchoring history to the latest Semantic Versioning tag.

Why does my changelog show an Unreleased section instead of a new version number?

An Unreleased section appears when changes are detected between HEAD and the latest SemVer tag but no new version tag has been created, grouping pending commits until the next semantic version release.