changelog-generation

Generate stakeholder-friendly changelogs from merged pull requests.

4|Updated Apr 20, 2018
One-click install
npx skills add https://github.com/entorenee/dotfiles --skill changelog-generation-entorenee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generation
Source: https://github.com/entorenee/dotfiles/tree/main/nix/module/claude/config/skills/changelog-generation
Command: npx skills add https://github.com/entorenee/dotfiles --skill changelog-generation-entorenee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms technical pull request activity and deployment changes into concise, stakeholder-friendly changelogs, removing the need for manual summarization and translation of engineering changes into business-facing language.

Core Features & Use Cases

  • PR extraction and analysis: Identify individual PRs in a merge or branch range and extract titles and descriptions for summarization.
  • Classification and mapping: Classify changes into categories (New Features, Bug Fixes, Enhanced User Experience, plus a dynamic category) and map changed file paths to projects in monorepos.
  • Audience-focused formatting: Produce brief, non-technical bullet points organized by category or project for release notes and deployment announcements.
  • Use Case: After merging a release branch into main, generate a one-page release note highlighting user-facing features, fixes, and UX improvements for product and executive stakeholders.

Quick Start

Create concise release notes summarizing PRs merged into main for the latest deployment, organized by New Features, Bug Fixes, Enhanced User Experience, and an appropriate fourth category.

Frequently Asked Questions about changelog-generation

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

FAQPage Schema
How do I generate release notes from merged pull requests for stakeholders?

Generate release notes from merged pull requests by extracting PR titles and descriptions, classifying changes into categories like New Features and Bug Fixes, and producing concise non-technical bullet points for stakeholders.

What is the best way to create changelogs for a monorepo with multiple projects?

Create monorepo changelogs by mapping changed file paths to their corresponding projects, then summarizing the pull requests into categorized release notes organized by project for each deployment.

Can I summarize GitHub pull requests between tags or branches for deployment announcements?

Yes, you can summarize GitHub pull requests between branches, tags, or deployments by providing PR links or branch ranges to extract and categorize the merged changes into release notes.

How does categorizing pull requests into release notes work?

Categorizing pull requests works by extracting PR titles and descriptions, then classifying changes into New Features, Bug Fixes, Enhanced User Experience, and a dynamic fourth category to produce structured release notes.

Do I need to include PR links when generating stakeholder-friendly changelogs?

No, you do not need to include PR links in the final output. The generated changelog produces concise, non-technical release notes without PR links to keep the summary stakeholder-friendly.