skills.rest
SumitRajpal
SumitRajpalCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

changelog

Generate a Markdown changelog from Git history using conventional commits.

Updated Mar 24, 2026
Search Tags:#automation#git#changelog#markdown#release-notes#commit-history#conventional-commits
One-click install
npx skills add https://github.com/SumitRajpal/nextjs-claude-architecture --skill changelog-sumitrajpal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/SumitRajpal/nextjs-claude-architecture/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/SumitRajpal/nextjs-claude-architecture --skill changelog-sumitrajpal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically converts Git commit history into a structured changelog, reducing manual writing and ensuring release notes are consistent and up-to-date.

Core Features & Use Cases

  • Automatic categorization of commits into Features, Bug Fixes, Documentation, and Breaking Changes.
  • Includes Breaking Changes section when present and supports last-release tagging.
  • Generates a Markdown changelog suitable for CHANGELOG.md and release notes; for example, during release prep.

Quick Start

Run the changelog generator to process the latest commits since the most recent tag and output a Markdown changelog.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I generate a changelog from Git commit history?▼

To generate a changelog from Git commit history, you can parse conventional commit prefixes to automatically categorize commits into Features, Bug Fixes, Documentation, and Breaking Changes for structured Markdown release notes.

How do I group conventional commits into release notes sections?▼

Grouping conventional commits into release notes sections involves parsing commit prefixes to automatically categorize them into distinct Markdown sections for Features, Bug Fixes, Documentation, and Breaking Changes.

Can I automatically detect the last release tag for a Markdown changelog?▼

Yes, generating a Markdown changelog can automatically detect the last release tag to process only the latest commits since that tag, ensuring your release notes contain only recent changes.

Does this changelog generator support projects not using conventional commits?▼

No, this changelog generator applies specifically to projects using conventional commits, relying on commit prefixes to accurately categorize Features, Bug Fixes, Documentation, and Breaking Changes.

What is the best way to format Git release notes for CHANGELOG.md?▼

The best way to format Git release notes for CHANGELOG.md is to output a structured Markdown file with categorized sections for Features, Bug Fixes, Documentation, and Breaking Changes, including optional versioning support.

Why are my conventional commits not showing up as Breaking Changes in the changelog?▼

Conventional commits not showing as Breaking Changes in a changelog occurs because the Breaking Changes section is only included when present, requiring specific commit prefixes to trigger the categorization.

Related Skills

Explore More Software Engineering Skills→
jholhewresjholhewres
3

changelog-gen

Generate CHANGELOG.md files by parsing Git conventional commits.

Community
Intermediate
joaquimscostajoaquimscosta
21

generating-changelog

Analyze git commit history to generate formatted changelogs with version bumps.

Community
Advanced
srnicholssrnichols
5

release-notes

Generates release notes from Git history and CHANGELOG files.

Community
Intermediate
sunny0826sunny0826
3

release-notes

Categorize Git commit logs into structured release notes in Markdown.

Community
Intermediate