skills.rest
jikig-ai
jikig-aiOFFICIAL
Explore all skills by this author →
GitHub

changelog

Generate concise changelogs from GitHub PRs merged to main.

12|2|Updated Jan 27, 2026
Search Tags:#automation#changelog#devops#github#discord#pull-requests#release-notes
One-click install
npx skills add https://github.com/jikig-ai/soleur --skill changelog-jikig-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/jikig-ai/soleur/tree/main/plugins/soleur/skills/changelog
Command: npx skills add https://github.com/jikig-ai/soleur --skill changelog-jikig-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate concise, structured changelogs from recent merges to the main branch so engineering teams don't have to manually compile PR summaries, track breaking changes, or credit contributors.

Core Features & Use Cases

  • Analyze PR metadata, labels, linked issues, and descriptions to identify new features, bug fixes, performance and developer-experience improvements.
  • Highlight breaking changes first, group user-facing features and bug fixes, and include PR numbers and contributor shoutouts for traceability.
  • Produce outputs formatted for short-team channels (Discord) with length validation, include deployment notes (migrations, env updates), and provide a "quiet day" fallback when no merges exist.
  • Support daily or weekly cadences and can use gh CLI to fetch PR details and labels when available.

Quick Start

Create a daily changelog summarizing PRs merged to main in the last 24 hours, grouping new features, bug fixes, and breaking changes, and include PR numbers and contributor shoutouts.

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 automatically?▼

Generate changelogs by analyzing GitHub PR metadata, labels, and linked issues to automatically extract features, bug fixes, and breaking changes. This process uses pull request data to summarize recent merges to the main branch without manual compilation.

Can I format release notes for Discord with length limits?▼

Yes, you can format release notes for Discord by applying length validation to the generated changelog output. The formatting ensures the changelog fits Discord channel limits while including PR numbers, deployment notes, and contributor shoutouts.

Does the changelog generator work with the GitHub CLI?▼

Yes, the changelog generator works with the GitHub CLI to fetch PR details and labels. Using gh CLI provides direct access to GitHub pull request metadata needed to identify breaking changes and group user-facing features.

How do I highlight breaking changes and contributor names in release notes?▼

Highlight breaking changes and contributor names in release notes by structuring the changelog to feature breaking changes first. It groups user-facing features and bug fixes while including PR numbers and contributor shoutouts for traceability.

What happens to the changelog when there are no recent merges to main?▼

When there are no recent merges to main, the changelog generation provides a 'quiet day' fallback. This ensures your daily or weekly summary still posts a valid message to channels like Discord instead of failing or sending nothing.

Related Skills

Explore More Software Engineering Skills→
ybbms777ybbms777
1

changelog

Compile changelogs from merged pull requests using GitHub CLI.

Community
Intermediate
winsorllcwinsorllc

discord-notify

Send plain text messages and rich embeds to Discord channels via webhooks.

Community
Intermediate
bossjonesbossjones
1

release-notes-generator

Generate categorized release notes from Git commits and pull requests.

Community
Advanced
lodekeeperlodekeeper
4

release-notes

Generate Lodestar GitHub release headers and Discord announcements from changelogs.

Community
Intermediate