auto-update-changelog

Generate CHANGELOG.md entries for merged Pull Requests with version and date.

Updated May 31, 2026
One-click install
npx skills add https://github.com/zizzfizzix/agentic-engineering-framework --skill auto-update-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-update-changelog
Source: https://github.com/zizzfizzix/agentic-engineering-framework/tree/main/core/ai/skills/auto-update-changelog
Command: npx skills add https://github.com/zizzfizzix/agentic-engineering-framework --skill auto-update-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of updating the CHANGELOG.md file to reflect changes merged into the repository since the last release, streamlining the release management process.

Core Features & Use Cases

  • Automated CHANGELOG Entry Generation: Automatically generates and populates the CHANGELOG.md file with entries for merged Pull Requests.
  • Version and Date Customization: Allows setting the version and date manually or using defaults read from package.json.
  • Release Preparation: Useful for preparing releases by adding entries for new features, fixes, and other changes merged into the repository.

Quick Start

Run the auto-update-changelog skill to generate the CHANGELOG entries.

Frequently Asked Questions about auto-update-changelog

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

FAQPage Schema
How do I automate CHANGELOG.md updates for merged pull requests?

You can automate CHANGELOG.md updates by running a script that detects merged pull requests since your last release and generates categorized entries with author attribution directly into the file.

How does automated changelog generation handle conventional commits and PR categorization?

Automated changelog generation parses merged pull requests, applies conventional commit practices for categorization, respects supersede rules, and attributes changes to their original PR authors in the output.

Do I need a defined version in package.json to auto-generate release notes?

Yes, auto-generating release notes requires a project with a defined version. The tool reads default version and date values from package.json, though you can also set them manually during execution.

What is the best way to prepare a CHANGELOG.md file for a new release?

The best way to prepare a CHANGELOG.md for release is to automate the extraction of merged PRs since the last version, populating the file with structured entries for new features and fixes.

Can I manually override the version and date when updating a change log?

Yes, you can manually override the version and date for your change log entries. While the tool reads default values from package.json, it allows you to input custom version and date parameters.