changelog

Rewrites pending changeset files with consumer-facing descriptions matching CHANGELOG style.

6|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/northguild/gmt --skill changelog-northguild
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/northguild/gmt/tree/main/.agents/skills/changelog
Command: npx skills add https://github.com/northguild/gmt --skill changelog-northguild

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Pending changeset files in .changeset/ become the verbatim body of CHANGELOG.md entries when a release is cut, so a vague or developer-focused description ships directly to consumers. This Skill rewrites those descriptions before the PR merges, while the diff is still fresh. ## Core Features & Use Cases - Grounded rewriting: Analyzes the branch diff against main and reads existing CHANGELOG.md entries to match the established tone, length, and structure for each bump level (patch, minor, major). - Safety guardrails: Preserves the changeset frontmatter and filename, flags bump types that contradict the fix-to-patch and new-API-to-minor rule, and never runs changeset:version. - Accuracy enforcement: Verifies every named export exists in packages/*/src/ before mentioning it, and omits internal-only changes that consumers do not care about. - Use Case: Before merging a feature PR that adds new date formatting functions, run this Skill to turn a one-line changeset stub into a polished entry listing each new export, then review the before/after diff. ## Quick Start Ask the assistant to update the pending changeset descriptions for the current branch before merging the PR.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I write a good changeset description before merging a PR?▼

Lead with what consumers get rather than which files changed, name every new public export, and match the tone of recent CHANGELOG entries at the same bump level. This Skill automates that by reading the branch diff and existing changelogs, then rewriting the changeset body for your review.

How does the changesets tool turn changeset files into CHANGELOG entries?▼

The description in .changeset/<slug>.md is used verbatim as the body of the version entry written into each affected package's CHANGELOG.md when a maintainer runs changeset:version in a release PR. Merging a PR with a changeset publishes nothing by itself.

Should internal-only changes get a changeset entry?▼

No. Changes to skills, agent config, test infrastructure, or README files do not warrant a changeset entry by themselves. If a pending changeset exists only because of internal changes, the Skill flags it for the user instead of polishing it.

When should a changeset use patch versus minor bump type?▼

Bug fixes map to patch and new API additions map to minor. The Skill does not change the frontmatter, but it flags the bump type to the user when it contradicts this rule based on what the branch diff actually contains.

Can this Skill run changeset:version or publish a release?▼

No. It only edits the .changeset/*.md file body and shows a before/after diff for confirmation. Running changeset:version is a deliberate maintainer action performed in a separate release PR, and the Skill explicitly never runs it.