changelog-generator

Generate structured release notes and lint commits using Conventional Commits standards.

Updated Nov 3, 2016
One-click install
npx skills add https://github.com/xleliberty/mydotfiles --skill changelog-generator-xleliberty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/xleliberty/mydotfiles/tree/main/.config/.claude/plugins/cache/claude-code-skills/engineering-advanced-skills/2.1.2/changelog-generator
Command: npx skills add https://github.com/xleliberty/mydotfiles --skill changelog-generator-xleliberty

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill eliminates the manual effort and inconsistency involved in maintaining project release notes by automating the parsing of git history into structured, auditable changelogs.

Core Features & Use Cases

  • Conventional Commit Parsing: Automatically categorizes changes into sections like Added, Fixed, and Security based on commit types.
  • Semantic Versioning: Infers the appropriate version bump (major, minor, patch) based on commit history and breaking change detection.
  • CI/CD Integration: Validates commit messages in pull requests to ensure compliance with project standards before merging.

Quick Start

Use the changelog-generator skill to generate a markdown changelog entry for the version range between v1.2.0 and v1.3.0.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I generate release notes from conventional commits automatically?

Automating release notes from conventional commits involves parsing your git history to categorize changes into structured sections like Added, Fixed, and Security based on commit types.

How does semantic versioning inference work from git commit history?

Semantic versioning inference analyzes your git commit history to automatically determine the appropriate version bump—major, minor, or patch—based on detected commit types and breaking changes.

Can I validate pull request commit messages in CI/CD pipelines?

Yes, you can validate pull request commit messages in CI/CD pipelines to ensure compliance with conventional commits standards before merging, maintaining consistent project history.

What output formats are supported for changelog generation?

Changelog generation supports CI-friendly output formats including JSON and Markdown, rendering structured release notes from parsed repository histories across specified version ranges.

Do I need Python 3 to parse git history and render changelogs?

Yes, you need Python 3 to execute the commit parsing and changelog rendering logic across repository histories, as the automation scripts require this environment to run.