changelog-update

Generate changelog entries from git commits into Added, Changed, Fixed, and Breaking sections.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/jayteealao/Aperture --skill changelog-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-update
Source: https://github.com/jayteealao/Aperture/tree/main/.claude/skills/changelog-update
Command: npx skills add https://github.com/jayteealao/Aperture --skill changelog-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates changelog generation by deriving release notes from git commits.

Core Features & Use Cases

  • Automated changelog generation: Create or update a CHANGELOG.md by aggregating commits.
  • Categorization: Sort commits into Added, Changed, Fixed, and Breaking sections.
  • Monorepo support: Optionally filter commits by package directory in multi-package repos.
  • Format compatibility: Uses Keep a Changelog style by default and can adapt to project-specific formats.

Quick Start

Run the changelog-update skill to generate a changelog entry from the latest commits since the last release. Review and edit as needed before committing and creating a release.

Frequently Asked Questions about changelog-update

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

FAQPage Schema
How do I automate changelog generation from git commits?

Automate changelog generation by deriving release notes from git commits. The skill aggregates commit history, formats entries into Added, Changed, Fixed, and Breaking sections, and updates your changelog file automatically.

Can I filter commits by package for monorepo changelog generation?

Yes, monorepo changelog generation supports filtering commits by package directory. This allows you to generate package-specific release notes in multi-package repositories without mixing unrelated changes.

Does this changelog generator follow the Keep a Changelog format?

Yes, this changelog generator uses the Keep a Changelog format by default. It categorizes commits into standard Added, Changed, Fixed, and Breaking sections, and can adapt to project-specific formats if needed.

What is the best way to categorize git commits into release notes?

The best way to categorize git commits into release notes is to group them into Added, Changed, Fixed, and Breaking sections. This skill automates that sorting process directly from your commit history.

How to generate a ready-to-commit release message from recent commits?

Generate a ready-to-commit release message by running the skill against your latest commits. It creates or updates the changelog file and outputs a formatted release message you can commit directly.

Can I use this changelog automation for any project type?

Yes, you can use this changelog automation for any project type. It derives release notes directly from git commits, making it language-agnostic and compatible with any repository structure.