changelog

Generate CHANGELOG entries from Git tags and commit history.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/neolao/claude-plugin-vibe --skill changelog-neolao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/neolao/claude-plugin-vibe/tree/main/skills/changelog
Command: npx skills add https://github.com/neolao/claude-plugin-vibe --skill changelog-neolao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of updating the CHANGELOG.md from Git history, eliminating manual entry and reducing errors.

Core Features & Use Cases

  • Git History Analysis: Parses Git tags and commits to generate ChangeLog entries.
  • Version Management: Automatically updates CHANGELOG entries with new version tags.
  • Deduplication: Eliminates duplicate commits that have already been entered in the CHANGELOG.
  • Use Case: Ensure your project's CHANGELOG is always up-to-date with new releases and features.

Quick Start

Run /vibe:changelog to update the CHANGELOG.md from the current commit history.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I generate a changelog from Git commit history automatically?

To automate changelog generation from Git commit history, this Skill parses your Git tags and commits to create new CHANGELOG entries. It eliminates manual entry by ensuring your project documentation accurately reflects the latest code changes.

How do I update CHANGELOG.md from Git tags for a new version release?

You can update CHANGELOG.md from Git tags by running the changelog command. It analyzes your commit history and automatically appends new version entries to the project documentation, keeping it synchronized with your latest releases.

Does the automated changelog generation deduplicate commits already in the file?

Yes, automated changelog generation includes deduplication of commits. It checks the existing CHANGELOG.md and eliminates duplicate commits that have already been entered, ensuring no redundant entries appear in the updated documentation.

What is the best way to maintain accurate project documentation during version control?

The best way to maintain accurate project documentation is automating CHANGELOG updates directly from Git history. This approach maps version tags to commit history, reducing manual entry errors and ensuring documentation stays current with code changes.

Can I parse Git tags to create change log entries without manual entry?

Yes, you can parse Git tags to create change log entries without manual entry. This Skill analyzes version tags and commit history to automatically generate and update CHANGELOG.md entries, removing the need for manual documentation tracking.