skills.rest
Svenja-dev
Svenja-devCOMMUNITY
Explore all skills by this author →
GitHub

changelog-generator

Analyze Git history and convert commit messages into categorized release notes.

38|5|Updated Dec 18, 2025
Search Tags:#automation#git#changelog#documentation#release-notes#customer-friendly#commit-categorization
One-click install
npx skills add https://github.com/Svenja-dev/claude-code-skills --skill changelog-generator-svenja-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/Svenja-dev/claude-code-skills/tree/main/skills/changelog-generator
Command: npx skills add https://github.com/Svenja-dev/claude-code-skills --skill changelog-generator-svenja-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dieser Skill analysiert die Git-History, um automatisch kundenfreundliche Release Notes zu erstellen und technische Sprache in verständliche Beschreibungen zu übersetzen.

Core Features & Use Cases

  • Analysiert Git-History, kategorisiert Commits (Feat, Fix, BREAKING, Docs) in kundenfreundliche Abschnitte.
  • Erzeugt verständliche Release Notes für Stakeholder und Kunden.
  • Unterstützt verschiedene Ausgabe-Szenarien: pro Tag, zwischen Versionen (z.B. v1.2.0..v1.3.0), oder über einen definierten Zeitraum (--week).

Quick Start

Use the changelog-generator to produce notes for the current repository. Example usage: /changelog # Seit letztem Tag /changelog v1.2.0..v1.3.0 # Zwischen zwei Versionen /changelog --week # Letzte Woche /changelog --since=2025-12-01 # Seit Datum

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I convert git commit history into customer-friendly release notes?▼

You can generate release notes between two versions by specifying a tag range like v1.2.0..v1.3.0, which analyzes the Git history between those specific tags and produces a structured changelog categorized by features, fixes, and breaking changes.

Can I generate changelogs for a specific time period like the last week?▼

Yes, you can generate changelogs for a specific time period using the --week flag for the last week or --since=YYYY-MM-DD to filter commits from a specific date onwards, producing categorized summaries for that defined scope.

How are commits categorized when generating documentation from Git history?▼

Commits are categorized from Git history into distinct sections for features (Feat), fixes (Fix), breaking changes (BREAKING), and documentation (Docs), translating technical commit messages into understandable descriptions for stakeholders and customers.

Do I need any external dependencies to automate release notes generation from commits?▼

No external dependencies are required to automate release notes generation from commits, as the Skill operates without dependencies to analyze your repository's Git history and produce structured changelogs directly.

What is the best way to automate documentation for software releases from commit messages?▼

The best way to automate documentation for software releases is to parse commit messages directly from Git history, categorizing them into customer-friendly sections for features, fixes, and breaking changes to produce understandable release notes for stakeholders.

Related Skills

Explore More Content & Communication Skills→
Veloxia-agencyVeloxia-agency

changelog-generator

Generate markdown or JSON changelog entries from Conventional Commit histories.

Community
Advanced
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
pythoninthegrassespythoninthegrasses
1

changelog-automation

Generate changelogs and release notes from commits, PRs, and tags.

Official
Advanced
BridgingIT-GmbHBridgingIT-GmbH
4

changelog-generator

Convert Git commit history into structured customer-friendly release notes.

Official
Basic