skills.rest
Nabilhassan12345
Nabilhassan12345COMMUNITY
Explore all skills by this author →
GitHub

changelog

Generate categorized changelog files from significant PR commits.

Updated Apr 7, 2026
Search Tags:#automation#git#workflow#changelog#pr#release-notes
One-click install
npx skills add https://github.com/Nabilhassan12345/voice-ai-workspace --skill changelog-nabilhassan12345
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/Nabilhassan12345/voice-ai-workspace/tree/main/pipecat/.claude/skills/changelog
Command: npx skills add https://github.com/Nabilhassan12345/voice-ai-workspace --skill changelog-nabilhassan12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create changelog files for important commits in a PR, saving time and standardizing release notes.

Core Features & Use Cases

  • Automatically generate categorized changelog files in the changelog/ folder for significant commits, using types like added, changed, deprecated, removed, fixed, security, performance, and other.
  • Enforce PR-based naming conventions such as {PR_NUMBER}.added.md, {PR_NUMBER}.fixed.md, etc., to organize release notes.
  • Use case: when preparing a release, generate complete, well-structured changelog entries from the PR history.

Quick Start

Generate changelog files from the current PR, creating the appropriate 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 automate changelog creation from pull requests?▼

You can automate changelog generation by processing significant PR commits into categorized files within the changelog/ directory. This enforces PR-based naming conventions to standardize release notes.

What categories does an automated changelog generator use for release notes?▼

Changelog entries are categorized using standard types: added, changed, fixed, deprecated, removed, security, performance, and other. Each entry contains a single-line summary of the change.

Can I generate release notes from git commits without manual formatting?▼

Yes, you can generate properly formatted release notes directly from git PR history. The workflow outputs structured markdown files in the changelog/ directory, eliminating manual formatting during release preparation.

Does this changelog workflow require any specific dependencies or components?▼

No specific dependencies or components are required to use this changelog workflow. It operates independently to parse PR commits and generate the categorized markdown files in your repository.

What is the best way to organize changelog files for a large number of pull requests?▼

The best way to organize changelog files is using the PR-based naming scheme, formatting files as {PR_NUMBER}.{type}.md. This structures release notes by pull request and change category within the changelog/ folder.

Related Skills

Explore More Software Engineering Skills→
synqingsynqing
1

changelog-generator

Generate user-facing changelogs from git commits with categorized changes.

Community
Intermediate
meirmmeirm
13

writing-release-notes

Generate categorized markdown release notes from git history and version files.

Community
Advanced
arowinskiarowinski

pr

Create pull requests with titles and template-aligned bodies from git diffs.

Community
Intermediate
o9nno9nn

release-changelog

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

Official
Intermediate