changelog

Write and review bilingual CHANGELOG.md sections for software releases.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/Bascht74/videopodcast-magic --skill changelog-bascht74
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/Bascht74/videopodcast-magic/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/Bascht74/videopodcast-magic --skill changelog-bascht74

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a changelog section that a stranger can understand is hard: points written by the person who built the change often miss context, mix two numbers, or read as translations. This Skill enforces the structure, style, and read-back discipline for CHANGELOG.md sections in the videopodcast-magic project. ## Core Features & Use Cases - Bilingual sections: Every version carries an English half and a German half with the same number of points, where the German half is rethought in German rather than translated. - Group ordering and shape rules: Groups follow the Keep a Changelog order (Added, Changed, Deprecated, Removed, Fixed, Security, Tests, Documentation), each at most once, with Documentation last. - Point quality checklist: Rules for naming the changed thing on screen, one fact per point, the second half under Fixed, and an eight-question read-back before a section counts as done. - Use Case: A new version of the program is due. Use this Skill to draft the CHANGELOG.md section in both languages, decide which changes belong in it at all, and verify each point against the read-back list before release. ## Quick Start Write the CHANGELOG.md section for version 3.0.0 in both English and German following the changelog skill rules.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I write a changelog section for a new software version?▼

Start with the version heading in the form ## [number] - YYYY-MM-DD, then add groups in Keep a Changelog order: Added, Changed, Removed, Fixed, Tests, Documentation. Each point names the changed thing as it appears on screen, states what it was, what it is now, and what follows for the user.

How to keep English and German changelog entries consistent?▼

Write the English half first, then a line reading **Deutsch**, then the same points rethought in German rather than translated sentence by sentence. Both halves must hold the same number of points, and neither half may carry function words of the other language.

What changes should be excluded from a changelog?▼

Exclude editorial tidying, measurement findings that changed nothing, and workshop-only work such as renamed tests, guidelines, comments, or function names. When in doubt, leave it out; a short section where every point says something beats a long one where they drown.

Why should a Fixed changelog entry include what happens now?▼

A Fixed point that only describes what was wrong is a bug report, not news. The reader needs the second half stating the current behavior, so they know the fault is gone and what to expect when they use the program.

Can a changelog point contain two numbers?▼

Only if they cannot be mistaken for each other. Two numbers measuring different things in one point confuse readers; split them into separate points or express them in different units, and always include the setup a number needs to make sense.