changelog

Draft a CHANGELOG.md entry from merged PRs since the last release tag.

19|31|Updated May 29, 2025

Search Tags:#automation #changelog #release management #pull requests #grafana #pr workflow

Ready to run

npx skills add https://github.com/grafana/grafana-pathfinder-app --skill changelog-grafana

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/grafana/grafana-pathfinder-app/tree/main/.cursor/skills/changelog
Command: npx skills add https://github.com/grafana/grafana-pathfinder-app --skill changelog-grafana

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft a CHANGELOG.md entry from merged PRs since the last release tag. Categorizes by conventional-commit prefix (Added / Fixed / Chore / Security / Changed), rewrites PR titles into sentence-case narrative bullets with PR refs, and commits to the current branch without pushing. Use when preparing a release, or call this skill from /release-prep.

Core Features & Use Cases

Drafts CHANGELOG.md entries by aggregating merged PRs since the last tag.
Rewrites PR titles into sentence-case narrative bullets with PR refs for clear release notes.
Categorizes entries into Added, Fixed, Chore, Security, Changed, and enforces Grafana-style capitalization rules.

Quick Start

Run the changelog skill in the repository to generate the next CHANGELOG.md draft for review and release preparation.

Frequently Asked Questions about changelog

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

FAQPage Schema

How do I generate CHANGELOG.md entries from merged pull requests?▼

You can generate CHANGELOG.md entries by aggregating merged PRs since the last release tag using gh pr list. The tool categorizes entries by conventional-commit prefix and rewrites PR titles into sentence-case narrative bullets with PR references.

How does automatic changelog categorization work for release notes?▼

Automatic changelog categorization works by parsing conventional-commit prefixes from merged PR titles. Entries are sorted into Added, Fixed, Chore, Security, and Changed categories, with Grafana-style capitalization rules applied to format the narrative bullets.

What is the best way to automate release preparation workflows for Grafana?▼

Automating release preparation involves drafting version notes from merged PRs and categorizing them per Grafana style. You can invoke this process directly from a release-prep workflow to generate and locally commit the next CHANGELOG.md draft for review.

Does the changelog drafting process commit and push changes to the remote repository?▼

The changelog drafting process commits the generated CHANGELOG.md file locally to the current branch without pushing. This ensures release notes remain local for review before any remote repository updates occur.

Can I use this changelog generation tool with repositories that do not follow conventional commits?▼

This tool expects conventional-commit prefixes to categorize entries into Added, Fixed, Chore, Security, and Changed. Repositories lacking these prefixes may not be categorized correctly, resulting in unsorted or misclassified changelog entries.