skills.rest
Gorillaa-ai-org
Gorillaa-ai-orgOFFICIAL
Explore all skills by this author →
GitHub

changelog

Generate changelog entries from PR commits into PR-numbered markdown files.

Updated Mar 3, 2026
Search Tags:#automation#git#changelog#pr#release-notes#conventional-commits
One-click install
npx skills add https://github.com/Gorillaa-ai-org/pipecat --skill changelog-gorillaa-ai-org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/Gorillaa-ai-org/pipecat/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/Gorillaa-ai-org/pipecat --skill changelog-gorillaa-ai-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changelog generation for PRs automates the creation of standardized release notes from commit history, eliminating manual note-taking.

Core Features & Use Cases

  • Automatic classification of commits into conventional changelog types (added, changed, deprecated, removed, fixed, security, performance, other) based on PR content.
  • Skips changelog entries for documentation-only, internal refactoring, test-only, and CI changes, ensuring release notes stay relevant.
  • Generates changelog files in the changelog/ folder named by PR number and type (e.g., 1234.added.md, 1234.changed.md) to support release workflows.

Quick Start

Run the changelog skill on a PR branch to generate corresponding changelog entries in the changelog/ folder.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I generate changelog entries from git PR commits?▼

This skill automates changelog generation by parsing git history and mapping PR commits to conventional changelog types, creating categorized markdown files in the changelog/ folder named by PR number and type.

How are conventional commits mapped to release notes categories?▼

Commits are classified into conventional types such as added, changed, fixed, security, and performance based on PR content, ensuring standardized release notes generation across software projects.

Does the changelog generator skip documentation and CI changes?▼

Yes, it skips documentation-only, internal refactoring, test-only, and CI changes, ensuring release notes remain strictly relevant to core application logic and feature updates.

What naming scheme is used for generated changelog files?▼

Generated changelog files use a PR-number-based naming scheme with the change type appended, such as 1234.added.md or 1234.changed.md, exported directly to the changelog/ folder.

What is the best way to automate PR changelogs for faster releases?▼

Automating PR changelogs for faster releases is handled by running this skill on PR branches, which parses git history and automatically generates standardized release notes files.

Related Skills

Explore More Software Engineering Skills→
dtsongdtsong
1

GitHub Changelog

Generate changelogs from merged pull requests and commits using GitHub CLI.

Community
Intermediate
adriannoesadriannoes
46

update-changelog

Parse repository tags and commit history to generate markdown changelog entries.

Community
Basic
zhangzhang-111-izhangzhang-111-i
2

changelog-generator

Generate changelog entries from Conventional Commits in markdown or JSON.

Community
Intermediate
nmdranmdra
26

keep-a-changelog

Parse Git commit history and format CHANGELOG.md entries per Keep a Changelog standards.

Community
Intermediate