skills.rest
haJ1t
haJ1tCOMMUNITY
Explore all skills by this author →
GitHub

auto-changelog

Generate CHANGELOG.md from git commit history using Conventional Commits.

Updated May 24, 2026
Search Tags:#git integration#SemVer#changelog generation#release documentation#CI/CD pipeline
One-click install
npx skills add https://github.com/haJ1t/senior-dev-squad-skills --skill auto-changelog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-changelog
Source: https://github.com/haJ1t/senior-dev-squad-skills/tree/main/plugins/senior-dev-squad/skills/auto-changelog
Command: npx skills add https://github.com/haJ1t/senior-dev-squad-skills --skill auto-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of CHANGELOG.md and release notes, reducing the manual effort required to document changes between software releases.

Core Features & Use Cases

  • Automated Changelog: Generates CHANGELOG.md based on commit history, categorized and formatted according to keepachangelog.com guidelines.
  • SemVer Versioning: Determines the correct version bump (major, minor, patch) based on commit types and changes.
  • Release Notes: Produces user-friendly release notes that are clear and concise, detailing new features, fixes, and breaking changes.
  • Use Case: Use this Skill in your CI/CD pipeline to ensure that your CHANGELOG.md is always up-to-date with your commit history, streamlining the release process.

Quick Start

Use the auto-changelog skill to generate a new CHANGELOG entry for the latest commit.

Frequently Asked Questions about auto-changelog

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

FAQPage Schema
How do I automate changelog generation from git commit history?▼

You can automate changelog generation by parsing git commit history to categorize changes and format them into a CHANGELOG.md file based on Conventional Commits and keepachangelog.com guidelines.

What is SemVer versioning and how does it apply to release documentation?▼

SemVer versioning determines the correct version bump (major, minor, or patch) for release documentation by analyzing commit types and breaking changes from your git history.

Can I use automated changelog generation in a CI/CD pipeline?▼

Yes, you can integrate automated changelog generation into your CI/CD pipeline to ensure your CHANGELOG.md stays up-to-date with commit history, streamlining the release process.

Do I need git installed to generate a CHANGELOG.md from commits?▼

Yes, git is required to generate a CHANGELOG.md because the tool analyzes your local commit history to identify features, fixes, and breaking changes for release notes.

How are breaking changes and new features categorized in release notes?▼

Breaking changes and new features are categorized in release notes by parsing Conventional Commits from your git history, producing clear and concise documentation detailing each change type.

What is the best way to keep a CHANGELOG.md up-to-date without manual effort?▼

The best way to keep a CHANGELOG.md up-to-date without manual effort is automating the process in your CI/CD pipeline, generating categorized release notes directly from commit history.

Related Skills

Explore More Software Engineering Skills→
sambersamber
178

conventional-git

Standardize Git commit messages and branch naming using Conventional Commits v1.0.0 rules.

Community
Advanced
sachinnair90sachinnair90

ci-validation-gates

Validate semver, token types, retries, and draft-release triggers in GitHub Actions publish workflows.

Community
Advanced
coff33ninjacoff33ninja

release-changelog

Automates SemVer-Compliant release workflows including bumping versions, updating changelogs, and triggering CI/CD pipelines for diverse programming languages and systems.

Community
Advanced
tizeetizee
3

changelog

Generate and update CHANGELOG.md from git commit history.

Community
Advanced