changelog-updater

Add dated SEM-formatted version entries to CHANGELOG.md.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/arrrrny/cli_sync --skill changelog-updater-arrrrny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-updater
Source: https://github.com/arrrrny/cli_sync/tree/main/skills/changelog
Command: npx skills add https://github.com/arrrrny/cli_sync --skill changelog-updater-arrrrny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates SEM-formatted changelog updates by adding a new dated version entry to the changelog, reducing manual edits and ensuring consistency.

Core Features & Use Cases

  • Create or prepend SEM-formatted version entries with the current date, version number, and a description of changes.
  • Format and organize entries according to SEM categories (Added, Changed, Fixed, etc.) for clear release notes.
  • Handle missing files and duplicates by creating the changelog when needed and avoiding duplicate version entries.
  • Use case: Prepare release notes for a new software version by programmatically updating CHANGELOG.md.

Quick Start

Add a new SEM-formatted changelog entry for a given version with its date and changes to the top of CHANGELOG.md.

Frequently Asked Questions about changelog-updater

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

FAQPage Schema
How do I automatically add a new version entry to a SEM changelog?

To automatically add a new version entry to a SEM changelog, the skill prepends a dated section with the version number and change descriptions to the top of CHANGELOG.md, ensuring consistent release documentation without manual edits.

Can I create a CHANGELOG.md file if it does not already exist in my project?

Yes, you can create a CHANGELOG.md file if it does not exist. The skill handles missing files by automatically generating the changelog and formatting the initial SEM version entry during the update process.

How do I format release notes into SEM categories like Added, Changed, and Fixed?

Formatting release notes into SEM categories involves organizing change descriptions under specific headers like Added, Changed, and Fixed. The skill structures these entries automatically when prepending the new version to CHANGELOG.md.

Will the changelog updater prevent duplicate version entries in markdown files?

Yes, the changelog updater prevents duplicate version entries in markdown files. It checks existing content in CHANGELOG.md and deduplicates top entries to avoid redundant release notes during automated updates.

What is the best way to maintain consistent changelog formatting for local software releases?

The best way to maintain consistent changelog formatting for local software releases is to automate SEM-formatted updates. Programmatically prepending dated version entries to CHANGELOG.md reduces manual edits and enforces category organization.