changelog

Aggregate merged pull requests into human-friendly changelogs for engineering teams.

25|15|Updated Aug 2, 2021

Search Tags:#automation #changelog #engineering #pr #pull-request #release-notes

Ready to run

npx skills add https://github.com/JesusFilm/core --skill changelog-jesusfilm

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aggregates and formats merged pull requests into human-friendly changelogs for internal engineering teams.

Core Features & Use Cases

Automated changelog generation: Summarizes PRs merged to main into a clear, readable log.
Contributor attribution: Credits authors and reviewers for each item.
Reference-worthy outputs: Includes issue references and optional notes on breaking changes.
Cadence support: Tailors outputs for daily or weekly release cycles.

Quick Start

Generate a concise daily changelog for the latest PR merges to main, including features, bug fixes, and contributor credits.

Frequently Asked Questions about changelog

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

FAQPage Schema

How do I generate a changelog from merged pull requests?▼

To generate a changelog from merged pull requests, you can aggregate and format PR metadata such as titles, descriptions, labels, and merge dates into a human-friendly log for your engineering team. This process summarizes features and bug fixes while crediting contributors.

What is the best way to automate release notes for daily engineering cycles?▼

Automating release notes for daily engineering cycles involves parsing merged pull request metadata and formatting it into readable summaries. This tailored output includes contributor attribution, issue references, and optional breaking change notes for transparent internal reviews.

Can I include breaking changes and issue references in an automated changelog?▼

Yes, an automated changelog can include breaking changes and issue references. By parsing pull request metadata, the output specifically formats issue references and optional notes on breaking changes alongside standard feature and bug fix summaries.

How do changelogs handle contributor attribution for merged PRs?▼

Changelogs handle contributor attribution by extracting author and reviewer information from merged pull request metadata. This data is then formatted directly into the human-friendly change log to credit the specific individuals involved in each item.

Does automated changelog generation work for weekly project handoffs?▼

Yes, automated changelog generation works for weekly project handoffs. It supports both daily and weekly release cycles by aggregating merged pull requests into transparent logs that document changes, issue references, and contributor credits for internal reviews.

What PR metadata is needed to format human-friendly release notes?▼

To format human-friendly release notes, the required pull request metadata includes the PR title, description, labels, merge date, author attribution, and issue references. This information is parsed to document features and flag breaking changes.