generate-changelog

Generate categorized changelogs from commit histories and PR descriptions.

3|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/dvy1987/agent-loom --skill generate-changelog-dvy1987
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: generate-changelog
Source: https://github.com/dvy1987/agent-loom/tree/main/.agents/skills/generate-changelog
Command: npx skills add https://github.com/dvy1987/agent-loom --skill generate-changelog-dvy1987

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Many projects accumulate noisy commit messages, PRs, and internal notes that are not immediately useful to end users or stakeholders. This Skill transforms raw repository activity into concise, user-facing release notes that highlight user value, call out breaking changes, and omit internal-only noise.

Core Features & Use Cases

  • Categorization: Groups changes into user-facing sections such as Added, Changed, Fixed, Deprecated, Removed, and Breaking Changes following the Keep a Changelog guidance.
  • Value-focused synthesis: Converts multiple related commits and PRs into one-sentence value statements that explain why a change matters.
  • Release publishing: Drafts a release summary, presents an executive summary, and saves the changelog to docs/changelogs while appending a record to docs/skill-outputs/SKILL-OUTPUTS.md.
  • Use Case: Prepare release notes before tagging a new version, produce internal or public changelogs, or summarize recent development activity for stakeholder updates.

Quick Start

Generate a changelog summarizing commits from the last tag to HEAD, highlight breaking changes, and save the result to docs/changelogs/vX.X.X.md.

Frequently Asked Questions about generate-changelog

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

FAQPage Schema
How do I generate release notes from git commit history?▼

To generate release notes from commit history, this Skill synthesizes raw commits and PR descriptions into categorized changelog sections following the Keep a Changelog template. It converts noisy repository activity into concise, user-facing value statements.

What is the best way to summarize pull requests for a software release?▼

The best way to summarize pull requests for a release is to group related PRs into categorized sections such as Added, Changed, Fixed, and Breaking Changes. This process converts internal development activity into user-facing value statements.

How do I format changelog entries using the Keep a Changelog standard?▼

Formatting changelog entries using the Keep a Changelog standard involves organizing changes into specific categories like Added, Changed, Fixed, Deprecated, and Removed. This Skill automatically applies that structure to synthesize your commit history.

Can I automatically categorize breaking changes from recent commits?▼

Yes, you can automatically categorize breaking changes from recent commits. The Skill analyzes raw commit histories and PR descriptions to identify and isolate breaking changes into a dedicated user-facing section within the changelog.

How do I prepare a changelog before tagging a new release version?▼

To prepare a changelog before tagging a new version, this Skill summarizes commits from the last tag to HEAD. It produces a categorized release summary and saves the output directly to your docs folder for immediate publication.