changelog

Generate CHANGELOG.md entries from merged GitHub pull requests since the last release tag.

5|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/ably/ably-ai-transport-js --skill changelog-ably
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/ably/ably-ai-transport-js/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/ably/ably-ai-transport-js --skill changelog-ably

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns merged pull requests into a polished CHANGELOG.md entry so release notes are accurate, consistent, and quick to publish.

Core Features & Use Cases

  • Release summarization: Collects merged PRs since the last tag and converts them into concise, user-facing bullets.
  • Versioned changelog editing: Inserts the new release block at the top of CHANGELOG.md while preserving the existing history and formatting.
  • Review-safe filtering: Skips internal, CI, and formatting-only work when it does not need to appear in the public changelog, while still supporting full summaries when needed.
  • Use case: A maintainer preparing a package release can generate the next changelog section from GitHub PRs, review the drafted bullets, and publish with confidence.

Quick Start

Use the changelog skill to create the next release entry from merged pull requests and update CHANGELOG.md for review.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I generate release notes from merged pull requests for a GitHub release?

Generate release notes by collecting merged pull requests since the last git tag and converting them into user-facing bullets for your changelog. This Skill automates the process by gathering GitHub PR metadata to draft review-ready release summaries.

What is the best way to update CHANGELOG.md without breaking existing formatting?

Update CHANGELOG.md by inserting the new release block at the top while preserving the existing history and formatting. The Skill performs markdown editing to safely add the new versioned entry without disrupting the document structure.

Can I automatically skip internal CI changes when drafting changelog entries?

Yes, you can skip internal CI changes when drafting changelog entries through review-safe filtering. The Skill omits internal, CI, and formatting-only work from the public changelog while still supporting full summaries if you need them documented.

Does this changelog generator work with git tags and GitHub PR metadata?

Yes, this changelog generator works directly with git tags and GitHub PR metadata. It identifies all merged pull requests occurring since your last release tag to ensure accurate and complete version summaries for your release preparation.

How do I add compare links to my markdown release notes?

Add compare links to markdown release notes by generating a review-ready release block that includes GitHub compare links between tags. The Skill constructs these links automatically as part of the changelog entry to provide context for the changes.

What should I do if my changelog formatting is not preserved when adding a new release?

If your changelog formatting is not preserved, ensure the markdown editing is strictly inserting the new release block at the top. The Skill is designed to maintain your existing changelog structure and history while adding the new entries.