skills.rest
PlagueHO
PlagueHOCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release-changelog

Update CHANGELOG.md and create a release tag from commits since the last version tag.

4|Updated Mar 18, 2026
Search Tags:#automation#git#changelog#versioning#release#tagging#ci
One-click install
npx skills add https://github.com/PlagueHO/plagueho.skills --skill release-changelog-plagueho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/PlagueHO/plagueho.skills/tree/main/plugins/github-workflows/skills/release-changelog
Command: npx skills add https://github.com/PlagueHO/plagueho.skills --skill release-changelog-plagueho

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Automates the release process by updating the CHANGELOG.md and tagging a new release based on commits since the last version tag.

Core Features & Use Cases

  • Detect the last release tag and compute commits since then
  • Categorize changes according to Keep a Changelog
  • Create or update CHANGELOG.md, commit, tag, and push to remote

Quick Start

Run the release workflow to update CHANGELOG.md and create a new git tag for the next version.

Frequently Asked Questions about release-changelog

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

FAQPage Schema
How do I automate changelog generation from git commits in a CI pipeline?▼

Automating changelog generation involves detecting the last git tag, categorizing subsequent commits, and updating CHANGELOG.md automatically within your CI pipeline to streamline release preparation.

What is the best way to automate git tagging and release notes creation?▼

The best way to automate git tagging and release creation is running a workflow that computes commits since the last version tag, updates CHANGELOG.md, and pushes the new tag to your remote repository.

Do I need a CHANGELOG.md file in my repository to automate release tagging?▼

Yes, a CHANGELOG.md file in the repository root is required. The workflow accesses this file to append categorized changes and uses git commands to detect the last tag and push updates.

How does Keep a Changelog categorization work for git release tags?▼

It works by parsing commits made since the last version tag and sorting them into standardized categories to automatically update the CHANGELOG.md file for the new release.

Can I use this automated release workflow without a CI pipeline?▼

Yes, you can run it locally, but you need git command access. The workflow is designed for CI pipelines but fundamentally relies on git to detect tags, commit changes, and push to a remote.

Related Skills

Explore More Software Engineering Skills→
evolution-foundationevolution-foundation
520

dev-release

Generate a changelog, bump semantic versions, and create a release commit and tag.

Official
Advanced
psmonpsmon
8

agent-zero-build

Automate AgentZero Lite releases by syncing work, bumping versions, and pushing annotated tags.

Community
Advanced
jikimejikime
5

jikime-workflow-changelog

Generate categorized changelogs from Git commits with breaking change detection.

Community
Advanced
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced