skills.rest
surfingalien
surfingalienCOMMUNITY
Explore all skills by this author →
GitHub

changelog-generator

Generates user-facing changelogs by analyzing and categorizing git commit history.

1|Updated May 6, 2026
Search Tags:#changelog#versioning#documentation#release notes#product updates#git commits
One-click install
npx skills add https://github.com/surfingalien/FinSurfing --skill changelog-generator-surfingalien
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/surfingalien/FinSurfing/tree/main/Downloads/FinSurfing/.agents/skills/changelog-generator
Command: npx skills add https://github.com/surfingalien/FinSurfing --skill changelog-generator-surfingalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing release notes from raw git commits is tedious and time-consuming, and technical commit messages rarely translate into language customers understand. This Skill automates the transformation of commit history into polished, user-friendly changelogs. ## Core Features & Use Cases - Commit Analysis & Categorization: Scans git history for a date range or between versions and groups commits into features, improvements, bug fixes, breaking changes, and security updates. - Technical-to-User Translation: Converts developer-oriented commit messages into clear customer-facing language while filtering out internal noise like refactoring and test commits. - Use Case: Before shipping version 2.5.0, run the Skill against all commits since v2.4.0 to produce a structured CHANGELOG.md entry ready for GitHub releases, app store submissions, or email announcements. ## Quick Start From your repository root, ask the AI to create a changelog from all commits since the last release.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I generate a changelog from git commits automatically?▼

Run the Skill from your git repository root and specify a scope, such as commits since the last release or a date range. It analyzes the commit history, categorizes changes, and outputs a formatted changelog in Markdown.

How to write release notes that users actually understand?▼

Translate technical commit messages into customer-facing language focused on user benefit, group them into features, improvements, and fixes, and exclude internal changes like refactoring. This Skill performs that translation automatically.

Can I generate a changelog for a specific date range or version?▼

Yes. You can specify commits between two dates, since a particular version tag like v2.4.0, or from the past week. The Skill scopes its git history analysis to the range you provide.

Does the changelog generator filter out internal commits?▼

Yes. It excludes noise such as refactoring, test updates, and other internal-only commits, keeping the changelog focused on changes that matter to end users.

Can I enforce a custom changelog style or format?▼

Yes. You can point the Skill to a style guide file such as CHANGELOG_STYLE.md, and it will apply your formatting conventions and brand voice to the generated output.

Related Skills

Explore More Product & Management Skills→
stacklokstacklok
2.0k

commit-message

Generates commit messages from staged files for common use cases.

Official
Intermediate
Kilo-OrgKilo-Org
166

changelog-generator

Generate user-facing changelogs from Git history with categorized release notes.

Official
Intermediate
Eric-Pacheco95Eric-Pacheco95

release-notes

Generate Markdown release notes from merged pull requests, closed tickets, and commit history.

Community
Advanced
marquesfelipmarquesfelip

automated-versioning

Automate semantic version bumps from conventional commits in CI/CD pipelines.

Community
Advanced