skills.rest
albertoirurueta
albertoiruruetaCOMMUNITY
Explore all skills by this author →
GitHub

setup-changelog

Backfill a missing CHANGELOG.md from git tags, GitHub Releases, and commit history.

Updated Jul 9, 2026
Search Tags:#changelog#git tags#commit history#release history#GitHub Releases
One-click install
npx skills add https://github.com/albertoirurueta/ai-catalog --skill setup-changelog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-changelog
Source: https://github.com/albertoirurueta/ai-catalog/tree/main/.claude/skills/setup-changelog
Command: npx skills add https://github.com/albertoirurueta/ai-catalog --skill setup-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

If a repository has release history but lacks a CHANGELOG.md, this Skill bootstraps one from scratch by exploring the actual release history (git tags, GitHub Releases, and code changes) and backfilling entries in Keep a Changelog format.

Core Features & Use Cases

  • Explore Release History: Uses git tags and, if hosted on GitHub, GitHub Releases, to reconstruct the release history.
  • Backfill Changelog: Fills in the missing changelog with entries for each past release.
  • Skip Existing Changelog: Stops the process if a CHANGELOG.md already exists to prevent merging with existing content.
  • Use Case: For a repository that has release history without a changelog file, this Skill can help create a comprehensive changelog based on real release information.

Quick Start

Run /setup-changelog to create a root CHANGELOG.md for your repository based on its release history.

Frequently Asked Questions about setup-changelog

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

FAQPage Schema
How do I generate a changelog from git tags and commit history?▼

You can generate a changelog from git tags by analyzing the repository's release history and commit history to backfill entries in Keep a Changelog format. This Skill reconstructs past releases to create a comprehensive CHANGELOG.md file.

Can I backfill missing changelog entries using GitHub Releases?▼

Yes, you can backfill missing changelog entries using GitHub Releases. The Skill explores GitHub Releases alongside git tags to reconstruct the release history and populate a new CHANGELOG.md file.

Does this tool work if my repository already has a CHANGELOG.md?▼

No, if a CHANGELOG.md already exists, the process stops to prevent merging with existing content. It is designed specifically to bootstrap a changelog from scratch for repositories lacking one.

What format does the generated changelog use?▼

The generated changelog uses the Keep a Changelog format. It backfills entries for each past release by analyzing git tags, GitHub Releases, and commit history.

When should I use an automated changelog generator?▼

You should use an automated changelog generator when your repository has release history but lacks a CHANGELOG.md file. It helps start a documented history by backfilling real release information from git tags.

Related Skills

Explore More Software Engineering Skills→
gittowergittower
413

release

Update changelog and version files from git history using semantic versioning.

Official
Advanced
ShiroiKuma0ShiroiKuma0
25

changelog

Update CHANGELOG.md with categorized user-facing release notes.

Community
Advanced
glinckerglincker
35

changelog-generator

Generate a CHANGELOG.md file from git commit history using Keep a Changelog format.

Official
Intermediate
mk-knight23mk-knight23
1

git-automator

Generate conventional commit messages, changelogs, and pull request descriptions from git history.

Community
Advanced