skills.rest
lolwierd
lolwierdCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

update-changelog

Aggregates git commits since the last tag into the Unreleased section of CHANGELOG.md.

1|1|Updated Aug 3, 2020
Search Tags:#automation#git#changelog#documentation#release#unreleased
One-click install
npx skills add https://github.com/lolwierd/dotfiles --skill update-changelog-lolwierd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-changelog
Source: https://github.com/lolwierd/dotfiles/tree/main/ai/dot-agents/skills/update-changelog
Command: npx skills add https://github.com/lolwierd/dotfiles --skill update-changelog-lolwierd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates updating repository changelogs by aggregating unreleased changes from commits since the last release into the Unreleased section.

Core Features & Use Cases

  • Baseline detection: automatically determine the most recent git tag as the baseline.
  • Change aggregation: collect commits not yet reflected in CHANGELOG.md (or CHANGELOG).
  • Unreleased updates: insert changes into the Unreleased section following the project's existing formatting.
  • Use Case: When preparing a new release, run this skill to surface all user-visible changes in a concise, changelog-ready format.

Quick Start

Run the changelog update on the main branch to refresh the Unreleased section with recent commits.

Frequently Asked Questions about update-changelog

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

FAQPage Schema
How do I automatically update an Unreleased section in a changelog from git commits?▼

To automatically update a changelog, this skill aggregates git commits since the last release tag and writes them into the Unreleased section of your CHANGELOG.md, preserving the existing formatting.

How does automatic baseline detection work for unreleased git changes?▼

Automatic baseline detection for unreleased changes works by identifying the most recent deterministic git tag in the repository and using it as the starting point to collect all subsequent commits.

Can I update my changelog without manually specifying the last release tag?▼

Yes, you can update your changelog without manually specifying a tag because the skill automatically derives the baseline release tag from your git history when it is not explicitly provided.

What is the best way to prepare a changelog for a new release using git?▼

The best way to prepare a changelog for a new release is to run this skill on your main branch, which will surface all user-visible changes from recent commits into a concise, changelog-ready format.

Do I need a specific file format to aggregate unreleased changes into my changelog?▼

You need a Git repository containing either a CHANGELOG.md or a CHANGELOG file to aggregate unreleased changes, ensuring the skill can read the existing content and append updates accurately.

Related Skills

Explore More Software Engineering Skills→
tizeetizee
3

changelog

Generate and update CHANGELOG.md from git commit history.

Community
Advanced
prof18prof18
1.1k

store-changelog

Generate app store release notes from git history since a specified tag.

Community
Intermediate
sambersamber
178

conventional-git

Standardize Git commit messages and branch naming using Conventional Commits v1.0.0 rules.

Community
Advanced
richardadonnellrichardadonnell
45

changelog-automation

Generate changelogs from commit history using Conventional Commits and Keep a Changelog format.

Community
Intermediate