changelog

Generate daily or weekly changelogs from merged PRs using the gh CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/xbpk3t/ce-codex --skill changelog-xbpk3t
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/xbpk3t/ce-codex/tree/main/skills/changelog
Command: npx skills add https://github.com/xbpk3t/ce-codex --skill changelog-xbpk3t

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changelog generation is manual and error-prone, making it hard to keep teams informed about what changed in the main branch.

Core Features & Use Cases

  • Automatic aggregation of PRs merged into main within a specified period.
  • Includes PR numbers, titles, contributors, and a concise summary of features and fixes.
  • Produces a readable release-note style changelog suitable for internal teams and stakeholders.

Quick Start

Trigger the changelog process for the daily period to generate yesterday's release notes from the main branch.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I generate release notes from merged GitHub PRs?

To generate release notes from merged GitHub PRs, this Skill automates fetching PR details using the gh CLI and aggregates titles, contributors, and PR numbers into a readable summary of features and fixes.

Can I automate a daily changelog summary for my main branch?

Yes, you can automate a daily changelog summary for your main branch. The process aggregates PRs merged within a specified daily or weekly period and highlights new features, bug fixes, and notable changes.

Do I need the gh CLI to automate changelog generation?

Yes, you need the gh CLI installed and authenticated. The changelog generation uses the gh CLI to fetch pull request details from your repository to trace PR numbers and contributor names.

How are breaking changes highlighted in automated release notes?

Automated release notes highlight breaking changes when present by explicitly separating them from standard new features and bug fixes during the PR aggregation process.

What is the best way to keep teams informed about main branch updates?

The best way to keep teams informed about main branch updates is to automatically produce release-note style changelogs. This reduces manual errors by providing a concise summary of features and fixes for stakeholders.