shared-changelog

Generate CHANGELOG.md from Git history using conventional commits.

3|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/edfenton/claude-skills --skill shared-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shared-changelog
Source: https://github.com/edfenton/claude-skills/tree/main/shared/shared-changelog
Command: npx skills add https://github.com/edfenton/claude-skills --skill shared-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate CHANGELOG.md from conventional commits with semantic versioning to streamline release notes.

Core Features & Use Cases

  • Automatically infer versions from commit history and group changes into standard sections (Features, Bug Fixes, etc.).
  • Support release automation and CI integration by producing consistent changelog output.
  • Provide templates and references for customization and collaboration workflows.

Quick Start

Run the generation script to create or update CHANGELOG.md from your Git history.

Frequently Asked Questions about shared-changelog

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

FAQPage Schema
How do I generate a changelog from conventional commits?

To generate a changelog from conventional commits, you can parse Git history to group commit types like feat and fix into standard sections, automatically inferring semantic version bumps to output an updated CHANGELOG.md.

How does semantic versioning infer version bumps from Git history?

Semantic versioning infers version bumps from Git history by parsing conventional commit types, mapping features to minor bumps and bug fixes to patch bumps, which automatically determines the next release version for your changelog.

Can I automate release notes in a CI CD pipeline using Git history?

You can automate release notes in a CI CD pipeline by parsing Git commit history to produce consistent changelog output, enabling automated version bumps and release management directly within your continuous integration workflows.

What is the best way to maintain a CHANGELOG.md for software projects?

The best way to maintain a CHANGELOG.md is automating generation from conventional commits, which groups entries into sections like Features and Bug Fixes to ensure consistent release documentation without manual updates.

Does automated changelog generation work without strict conventional commits?

Automated changelog generation requires strict conventional commits because it relies on parsing specific commit types like feat, fix, and perf to group changes correctly and infer accurate semantic versioning bumps.