changelog

Summarize recent main-branch merges into a developer-friendly changelog.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of changelogs for recent merges to the main branch, saving time and ensuring consistency across teams.

Core Features & Use Cases

  • Auto-detect merged PRs from main and generate a concise changelog with features, fixes, and credits.
  • Supports daily or weekly summaries and configurable time windows.
  • Generates a readable narrative suitable for internal release notes and team-wide updates.

Quick Start

Provide a concise changelog for the latest merges on 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 changelogs from merged PRs on the main branch?

Generate changelogs from merged PRs by summarizing main-branch merges into a developer-friendly format highlighting features, fixes, and contributor credits. The Skill aggregates recent GitHub pull request data to produce a readable narrative for internal release notes.

Can I create daily or weekly release notes from GitHub PR summaries?

Create daily or weekly release notes by configuring time windows to aggregate merged PRs. The Skill summarizes recent main-branch merges into a concise changelog suitable for team-wide updates and internal release notes.

Do I need the gh cli to fetch PR details for merge notes?

Fetching PR details for merge notes optionally uses the gh cli to inspect GitHub data, including PR labels and issues. This enables the Skill to auto-detect merged PRs and generate accurate contributor credits and feature summaries.

What is the best way to automate team communication for recent GitHub merges?

Automate team communication for recent GitHub merges by summarizing main-branch merges into a witty, readable changelog. The Skill formats PR summaries into a narrative highlighting features, fixes, and credits suitable for team-wide updates.

Does the changelog Skill support extracting PR labels and issues from GitHub?

The changelog Skill supports PR inspection via GitHub data, including PR labels and issues. It uses this data to aggregate multiple PRs and highlight features, fixes, and contributor credits in the generated release notes.

Are there limitations when generating changelogs for internal release notes?

Changelogs for internal release notes are generated from main-branch merges and expect output suitable for internal use. The Skill focuses on daily or weekly summaries and does not mention support for external public release formatting.