changelog-generator

Generate user-facing changelogs from git commit history.

Updated Jul 15, 2025
One-click install
npx skills add https://github.com/nicolas-deyros/astro-portfolio-v2 --skill changelog-generator-nicolas-deyros
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/nicolas-deyros/astro-portfolio-v2/tree/main/.agents/skills/changelog-generator
Command: npx skills add https://github.com/nicolas-deyros/astro-portfolio-v2 --skill changelog-generator-nicolas-deyros

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes git commit history to automatically generate clear, customer-facing release notes, saving time and eliminating manual drafting.

Core Features & Use Cases

  • Scans Git History: Analyzes commits from a specific time period or between versions to capture changes.
  • Categorizes Changes: Groups commits into logical categories (features, improvements, fixes, breaking changes, security).
  • Translates Tech → Customer Language: Converts technical commits into user-friendly, publish-ready notes.
  • Formats Professionally: Produces clean, structured changelog entries suitable for release pages and notices.
  • Maintains Brand Voice: Applies consistent tone and formatting to align with your product messaging.

Quick Start

Generate a changelog for commits since the last release in your repository.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I generate user-friendly release notes from git commits?

Generate user-friendly release notes from git commits by parsing commit history, categorizing changes into features or fixes, and translating technical messages into structured, publication-ready text.

Can I automatically categorize git commit messages into features and fixes?

Yes, you can automatically categorize git commit messages by parsing the commit history and grouping changes into logical categories such as features, improvements, fixes, breaking changes, and security.

Does this changelog generator work with commits across specific versions and time ranges?

Yes, this changelog generator works with commits across specific versions and time ranges, analyzing the git history within those boundaries to capture and structure all relevant changes.

What is the best way to translate technical git commits into customer communication?

The best way to translate technical git commits into customer communication is to parse the commit history, categorize the changes, and reformat the technical text into a consistent brand voice with publication-ready notes.

Do I need any dependencies to automate changelog generation from commit history?

No, you do not need any dependencies to automate changelog generation from commit history, as the process parses commit messages and formats them independently without external components.