changelog

Generate structured changelogs from merged GitHub PRs with daily or weekly windows.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/yxc023/agent-config-studio --skill changelog-yxc023
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/yxc023/agent-config-studio/tree/main/.opencode/skills/changelog
Command: npx skills add https://github.com/yxc023/agent-config-studio --skill changelog-yxc023

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating timely, readable changelogs from the latest PR merges into the main branch to keep teams aligned and informed.

Core Features & Use Cases

  • Automatically summarize PRs merged into main with feature highlights, bug fixes, and credits
  • Support daily and weekly time windows with clear headings and PR references
  • Generate output that includes PR numbers, contributor names, and issue links for traceability
  • Template-ready formatting suitable for product, marketing, or release notes

Quick Start

Generate a changelog for the latest daily merges into main.

Frequently Asked Questions about changelog

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

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

Automate release notes by summarizing GitHub PRs merged into the main branch. The tool extracts PR numbers, authors, and labels to generate structured summaries highlighting new features and bug fixes for product and marketing use.

Can I generate daily or weekly changelogs from GitHub main branch merges?

Yes, you can generate daily and weekly changelogs from main branch merges. The output features clear headings, PR references, contributor names, and issue links to keep teams aligned across specific time windows.

Does this changelog automation work with GitHub PR labels and issue links?

Yes, changelog automation uses GitHub data including PR numbers, authors, and labels. It produces a structured summary that integrates linked issues and PR references for full traceability in release notes.

What is the best way to format GitHub PR summaries for internal marketing teams?

The best way to format PR summaries for marketing teams is generating template-ready release notes. This approach categorizes PR merges into new features and bug fixes while crediting contributors for engaging internal updates.

Do I need any extra dependencies to automate internal changelogs from GitHub?

No extra dependencies are required to automate internal changelogs from GitHub. The tool operates independently to fetch PR data and output structured, release-note friendly summaries without external components.