Changelog

Generate user-facing changelogs from commits and pull requests via GitHub API.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/enuno/noesis-aeon --skill changelog-enuno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Changelog
Source: https://github.com/enuno/noesis-aeon/tree/main/skills/changelog
Command: npx skills add https://github.com/enuno/noesis-aeon --skill changelog-enuno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of user-facing changelogs from recent commits and pull requests across watched repositories, saving time and reducing manual effort.

Core Features & Use Cases

  • In-Repo Changelog: Automatically create a changelog within the repository itself.
  • Cross-Repo Changelog PR: Generate a changelog PR on a separate marketing/docs repository.
  • Keep a Changelog Format: Outputs changelogs in a standardized format that is easy to read and maintain.
  • Noise Filtering: Filters out bot authors, merge commits, and revert commits to focus on user-facing changes.
  • Categorization: Categorizes changes into Breaking, Added, Changed, Fixed, and Security.

Quick Start

Generate a changelog for the current repository using the changelog skill.

Frequently Asked Questions about Changelog

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

FAQPage Schema
How do I automate changelog generation from commits and pull requests?

Automate changelog generation by using the GitHub API to fetch recent commits and pull requests, filtering out noise, and categorizing changes into standardized groups. This Skill outputs a formatted changelog automatically from watched repositories.

How does noise filtering work when generating a changelog from GitHub?

Noise filtering removes bot authors, merge commits, and revert commits from the changelog generation process. This ensures only user-facing changes from pull requests and commits are categorized and included in the final output.

Can I generate a cross-repo changelog PR on a separate documentation repository?

Yes, cross-repo changelog mode generates a changelog PR on a separate marketing or docs repository. It compiles changes from watched repositories and submits the formatted output to your designated target repository.

Do I need the gh CLI to generate changelogs from GitHub repositories?

Yes, the gh CLI is required to access the GitHub API for fetching commits and pull requests. You must configure repository and branch settings to successfully generate the categorized changelog output.

What categories are used when generating a changelog from pull requests?

Changes from pull requests are categorized into Breaking, Added, Changed, Fixed, and Security. This standardized categorization follows the Keep a Changelog format for easy reading and maintenance.