changelog

Generate structured changelogs and release notes from git commit and PR history.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill changelog-arbazkhan971
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/changelog
Command: npx skills add https://github.com/arbazkhan971/godmode --skill changelog-arbazkhan971

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams create, maintain, and auto-generate clear, consistent changelogs and release notes from git commit and PR history so users and developers understand what changed, why, and how to migrate.

Core Features & Use Cases

  • Conventional Commits parsing to auto-generate categorized changelog entries and detect breaking changes.
  • Keep a Changelog formatting and templates for developer-facing and user-facing release notes.
  • Migration guide generation and explicit breaking-change communication for safe upgrades.
  • Release preparation workflows that analyze commits, tags, and PRs, link issues/PRs in entries, and enforce rules for auditing and automatic rollback when dates/versions are incorrect.

Quick Start

Ask the changelog skill to generate a CHANGELOG.md and release notes by analyzing commits and PRs since the last tag.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I generate release notes from git commit history?

To generate release notes, this skill parses your git commit and pull request history to automatically create structured, categorized entries in Keep a Changelog format. It analyzes commits since your last tag to identify changes, link issues, and output human-facing notes.

Can I auto-generate a changelog from Conventional Commits?

Yes, you can auto-generate a changelog from Conventional Commits. The skill parses Conventional Commit messages to categorize changelog entries automatically, detect breaking changes, and format the output according to Keep a Changelog standards for both developer and end-user audiences.

How do I create a migration guide for breaking changes?

You create a migration guide by analyzing commit and PR metadata to detect breaking changes. The skill identifies breaking changes parsed from your git history and generates explicit migration guide documentation to ensure safe upgrades and clear communication for downstream users.

Does this changelog generator work with Keep a Changelog formatting?

Yes, this changelog generator formats entries using the Keep a Changelog standard. It applies Keep a Changelog templates to parse PR metadata and conventional commits, linking issues and PRs while emitting both machine-readable changelogs and human-facing release notes.

What is the best way to enforce conventional commits for release preparation?

The best way to enforce conventional commits during release preparation is to analyze tags and PRs against predefined rules. The skill audits commit history, links related issues, and can trigger automatic rollback when dates or versions are incorrectly formatted.