changelog

Updates CHANGELOG.md with notable changes from git commits since the last release tag.

3|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/MaxWolf-01/agents --skill changelog-maxwolf-01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/MaxWolf-01/agents/tree/main/mx/skills/changelog
Command: npx skills add https://github.com/MaxWolf-01/agents --skill changelog-maxwolf-01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing release notes manually means digging through git history, deciding which commits matter, and formatting entries consistently. This Skill automates that process by reading commits since the last release tag and drafting properly formatted changelog entries. ## Core Features & Use Cases - Automatic Baseline Detection: Finds the most recent git tag with git describe --tags --abbrev=0 when no baseline version is provided. - Commit-to-Changelog Generation: Reviews commits between the baseline and HEAD, filters out insignificant changes (typos, internal refactors), and writes user-facing entries grouped by importance. - Style Preservation: Appends to the existing "Unreleased" section while matching the repository's heading style, bullet format, and ordering conventions. - Use Case: Before cutting a release, run this Skill to populate the Unreleased section of CHANGELOG.md with notable features, fixes, and breaking changes since the last tag, referencing PR numbers where available. ## Quick Start Update the changelog with all notable changes since the last release tag.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I update a changelog from git commits?

Run git log from the last release tag to HEAD, then filter commits for user-facing changes like features, fixes, and breaking changes. This Skill automates that flow using git describe --tags --abbrev=0 to find the baseline and writes entries into the Unreleased section.

How to generate release notes since the last git tag?

Use git describe --tags --abbrev=0 to identify the most recent tag, then git log <tag>..HEAD to list commits. The Skill converts notable commits into concise changelog entries, referencing PR numbers instead of raw commit hashes.

What changes should be included in a changelog?

Include notable user-facing changes: features, fixes, and breaking changes, ordered by importance. Exclude typo fixes, internal refactoring, minor documentation updates, and dependency bumps unless they fix security issues or add user-facing features.

Does this work if my repository has no CHANGELOG.md file?

Yes. If CHANGELOG.md does not exist, the Skill falls back to a file named CHANGELOG. It also works with different default branch names, treating the configured default branch as the current version instead of main.

Will it overwrite my existing Unreleased section?

No. If an Unreleased section already contains content, the Skill appends new entries rather than replacing them. It also preserves the existing heading style, bullet format, ordering, and spacing conventions.