skills.rest
a7garden
a7gardenCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release-changelog

Generate releases/v{version}.md from commits, changesets, and merged PRs since the last stable tag.

Updated Mar 15, 2026
Search Tags:#automation#git#changelog#versioning#documentation#release
One-click install
npx skills add https://github.com/a7garden/CoHalo --skill release-changelog-a7garden
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/a7garden/CoHalo/tree/main/skills/release-changelog
Command: npx skills add https://github.com/a7garden/CoHalo --skill release-changelog-a7garden

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CoHalo teams need an accurate, publish-ready release changelog that reflects changes since the last stable version. This skill automates gathering commit history, changesets, and merged PR context to produce a stable file.

Core Features & Use Cases

  • Identify the last stable tag and compute the delta since then.
  • Aggregate commits, changesets, and merged PR context into a single file (releases/v{version}.md).
  • Ensure idempotency: if the file already exists, present it for review instead of overwriting.

Quick Start

Run the release-changelog skill to generate the stable releases/v{version}.md file by analyzing commits, changesets, and merged PR context since the last stable tag.

Frequently Asked Questions about release-changelog

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

FAQPage Schema
How do I generate a release changelog from git commits and merged PRs?▼

Aggregate git commits, changesets, and merged PR context since the last stable tag to automatically produce a publish-ready releases/v{version}.md file.

What is the best way to automate changelog generation for stable version releases?▼

Automating changelog generation computes the delta since the last stable tag by reading commit history and changesets, producing an accurate, publish-ready file without manual aggregation.

Does this changelog automation overwrite existing release documentation?▼

This changelog automation is idempotent and does not overwrite existing files; if releases/v{version}.md already exists, it presents the file for review and guides updates or regeneration instead.

How do I identify changes since the last stable tag for changelog documentation?▼

Identify changes since the last stable tag by computing the delta of commits, changesets, and merged PR context, then aggregating that context into a single release documentation file.

Can I use changesets and merged PR context together to build a release changelog?▼

Yes, you can build a release changelog by aggregating changesets and merged PR context alongside commit history, combining all three data sources into a single releases/v{version}.md file.

Related Skills

Explore More Software Engineering Skills→
freire19freire19

release-setup

Generate release-please configuration, workflow, and baseline tags for Git repositories.

Community
Intermediate
kurokeitakurokeita
1

changelog-automation

Automate changelog generation from commits, PRs, and releases.

Community
Intermediate
Thank-you-LinusThank-you-Linus
206

release-stable

Automates stable release workflows by detecting beta finalization or direct stable releases.

Official
Advanced
Tonybleything76Tonybleything76

Changelog Generator

Generate changelog entries from Git commit history using Conventional Commits.

Community
Advanced