release-changelog

Name: release-changelog
Availability: InStock
Author: o9nn

Compile git commits, PR summaries, and change notes into a standardized changelog document.

Updated May 4, 2026

Search Tags:#automation #git #changelog #release management #release notes

Ready to run

npx skills add https://github.com/o9nn/entelechorg --skill release-changelog-o9nn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/o9nn/entelechorg/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/o9nn/entelechorg --skill release-changelog-o9nn

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the creation of comprehensive changelogs by aggregating commit history, merged PRs, and release notes, saving time during software releases.

Core Features & Use Cases

Changelog Generation: Automatically compiles a detailed release log based on git commits, PRs, and change notes.
Preset Formatting: Produces standardized changelog files for stable releases, including sections for breaking changes, improvements, fixes, and contributors.
Use Case: For a software project preparing a new release, invoke this Skill to create an accurate, formatted changelog document that can be published for users and stakeholders.

Quick Start

Use the release-changelog skill to generate a changelog file after completing a release, by running the script with the current repository state.

Frequently Asked Questions about release-changelog

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

FAQPage Schema

How do I automatically generate a changelog from git commit history?▼

To automatically generate a changelog from git commit history, this Skill parses your repository state and aggregates commit messages, PR summaries, and change notes into a standardized document. It structures the output into clear sections for breaking changes, fixes, and improvements.

What is the best way to compile release notes from merged PRs for a new software release?▼

Compiling release notes from merged PRs is best handled by aggregating PR summaries and change files into a structured changelog. This process ensures your release documentation accurately captures all project updates and communicates them transparently to users and stakeholders.

Can I format release notes into standardized sections for breaking changes and fixes?▼

Yes, you can format release notes into standardized sections for breaking changes, improvements, fixes, and contributors. This Skill applies preset formatting rules to your parsed git history and PR data to produce a consistent, structured changelog file for stable releases.

Does this changelog generation approach work without external dependencies?▼

Yes, this approach works without external dependencies. The Skill relies entirely on internal scripts and references to parse your existing git history, change files, and PR data, requiring no additional packages to produce the final structured changelog document.

When do I need to generate a structured changelog document for my software project?▼

You need to generate a structured changelog document when preparing a new software release. It maintains a clear release history, communicates project updates to users, and ensures development transparency by compiling aggregated commit messages and PR summaries into a standardized format.