changelog

Generate changelog files named by PR number and type from commit messages.

Updated Apr 1, 2025

Search Tags:#automation #git #changelog #commit #release #pr #file-naming

Ready to run

npx skills add https://github.com/toinfinityai/pipecat --skill changelog-toinfinityai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/toinfinityai/pipecat/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/toinfinityai/pipecat --skill changelog-toinfinityai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create changelog files for important commits in this PR. The PR number is provided as an argument.

Core Features & Use Cases

Generate per-PR changelog files under the changelog/ folder, named by PR_NUMBER and type (e.g., 1234.added.md).
Enforce standard types and file naming to maintain consistent release notes.
Use cases include release preparation, code review, and auditing changes across PRs.

Quick Start

Run the skill on the current PR to generate changelog files under changelog/ for each significant change, named by PR_NUMBER and type.

Frequently Asked Questions about changelog

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

FAQPage Schema

How do I automatically generate a changelog from git commits for a pull request?▼

To automatically generate a PR changelog from git commits, this skill inspects commits on the current branch and creates changelog files under the changelog/ folder. Each file is named using the PR number and change type, such as 1234.added.md, for release preparation.

What is the file naming format for PR changelog fragments during release preparation?▼

The file naming format for PR changelog fragments is {PR_NUMBER}.{type}.md, created under the changelog/ directory. This enforces standard types and consistent file naming to maintain structured release notes across pull requests.

How do I parse commit messages to categorize changes for release notes?▼

Parsing commit messages to categorize changes for release notes is handled by applying allowed types defined in the skill instructions. It processes each significant commit on the branch and generates the corresponding categorized markdown file.

Can I exclude specific commits from being included in the generated changelog?▼

Yes, you can exclude specific commits from the generated changelog. The skill handles exclusions as described in its instructions, ensuring only significant changes are parsed and output into the categorized markdown files during the workflow.

Does this changelog generation skill require any external dependencies?▼

No, this changelog generation skill does not require any external dependencies. It operates directly within your software engineering workflow to parse commit messages and generate the required markdown files.

When should I use automated changelog file generation in a CI workflow?▼

Automated changelog file generation should be used during PR review and release workflows. It audits changes across PRs by inspecting commits and creating structured markdown files, ensuring consistent release notes without manual entry.