changelog-generator

Drafts release notes as Changesets files for the Rove CLI package.

136|8|Updated May 9, 2026
One-click install
npx skills add https://github.com/Sma1lboy/rove --skill changelog-generator-sma1lboy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/Sma1lboy/rove/tree/main/.claude/skills/changelog-generator
Command: npx skills add https://github.com/Sma1lboy/rove --skill changelog-generator-sma1lboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing release notes by hand is error-prone: contributors edit generated CHANGELOG files directly, soft-wrap lines that break GitHub release rendering, and include internal refactors users do not care about. This Skill enforces Rove's Changesets-based workflow so release notes are consistent and render correctly. ## Core Features & Use Cases - Changeset authoring: Creates one .changeset/<name>.md file per user-facing change with the correct @sma1lboy/rove bump type (patch, minor, or major). - Commit filtering: Scans git log since the last release tag, skips changes already covered by existing changesets, and filters out internal-only commits like refactors and CI tweaks. - House style enforcement: Applies Rove's rules including single-line summaries (no soft wraps), present-tense user-perspective voice, and bold lead-in headlines. - Use Case: Before cutting a release, ask the Skill to review commits since v0.4.0 and backfill changesets for any user-facing changes that slipped through, so the generated CHANGELOG and GitHub release body are complete. ## Quick Start Ask the assistant to draft changesets for everything user-facing that changed since the last release tag in this repository.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I write release notes with Changesets?▼

Create one `.changeset/<name>.md` file per change with frontmatter mapping the package name to a bump type (patch, minor, or major) and a single-line summary below. Run `bun run changeset` for the interactive CLI, or hand-write the file when scripting a batch.

How do I generate a changelog from git commits?▼

Run `git log --no-merges <last-tag>..HEAD` to list commits since the last release, then filter for user-facing changes and check existing `.changeset/*.md` files to avoid duplicates. Write one changeset per coherent change rather than dumping raw commit messages.

Should I edit CHANGELOG.md directly when using Changesets?▼

No. The CHANGELOG is generated by `changeset version` at release time from the pending `.changeset/*.md` files. Hand-editing it or adding an Unreleased section conflicts with the automated release flow.

Why does my GitHub release text render with hard line breaks?▼

GitHub renders release bodies with GFM hard breaks, so every newline inside a paragraph becomes a visible line break. Keep each changeset summary on a single line, even if it is hundreds of characters long, so the release page renders flowing text.

What changes should be excluded from release notes?▼

Skip pure refactors, internal test additions, docs and config tweaks, dependency bumps with no behavior change, and CI adjustments. If a change needs no release entry but should be recorded, use `bun run changeset -- --empty`.