generate-changelog

Generates and updates CHANGELOG.md entries from release-notes markdown files following Keep a Changelog and SemVer.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/lucaszhh/agents --skill generate-changelog-lucaszhh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: generate-changelog
Source: https://github.com/lucaszhh/agents/tree/main/skills/generales/generate-changelog
Command: npx skills add https://github.com/lucaszhh/agents --skill generate-changelog-lucaszhh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually compiling changelogs from scattered release notes and merge request titles is error-prone and often produces duplicated versions, raw commit hashes, or corrupted history. This Skill standardizes the process by converting release-notes markdown files into structured, Spanish-language CHANGELOG.md entries. ## Core Features & Use Cases - Structured changelog generation: Classifies changes into Keep a Changelog categories (Añadido, Cambiado, Corregido, Eliminado) grouped by module or component. - Duplicate protection: Verifies via grep that a version does not already exist before writing, preventing duplicated entries. - Direct-to-disk writing: Updates CHANGELOG.md in place without dumping the full file into the chat, reporting only quantitative metrics. - Use Case: After a release, point the agent at release-notes/backend-release-notes.md and it inserts a new [6.22.0] - 2026-09-08 section at the top of CHANGELOG.md, preserving all prior version history. ## Quick Start Generate the changelog for version 6.22.0 using the release notes in the release-notes folder and update CHANGELOG.md.

Frequently Asked Questions about generate-changelog

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

FAQPage Schema
How do I generate a CHANGELOG.md from release notes automatically?▼

Place your release notes as markdown files in a release-notes/ folder, then invoke the skill with the target version. It classifies each change into Keep a Changelog categories, groups them by module, and inserts the new version section directly into CHANGELOG.md.

How to update a changelog without duplicating a version entry?▼

The skill runs a grep check for the version header before writing. If the version already exists, it alerts you and asks for confirmation to update the existing entry instead of creating a duplicate.

What format does the generated changelog follow?▼

It follows Keep a Changelog with Semantic Versioning, written in neutral formal Spanish. Entries use the categories Añadido, Cambiado, Corregido, and Eliminado, with changes grouped under module or component headings.

What happens if the release-notes folder is missing or empty?▼

The skill warns that no release notes were found and offers alternatives, such as processing commits from the current branch against develop using git log, or accepting a manually provided notes file path.

Does the changelog include commit hashes or branch names?▼

No. Raw commit hashes and branch names are explicitly prohibited. Each change is rewritten as a semantic, human-readable description so the changelog stays understandable to non-technical readers.

When should I not use this changelog generation approach?▼

Do not use it for generating pull request descriptions or QA test matrices, which are handled by separate skills. It is also unsuitable when you need changelogs in languages other than Spanish without adapting the template.