changelog-writer

Generates changelogs and release notes from git commit history following Keep a Changelog format.

2|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/sathishssj3/NexVR-Engine --skill changelog-writer-sathishssj3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-writer
Source: https://github.com/sathishssj3/NexVR-Engine/tree/main/.agents/skills/changelog-writer
Command: npx skills add https://github.com/sathishssj3/NexVR-Engine --skill changelog-writer-sathishssj3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing changelogs and release notes manually from raw git history is tedious and error-prone, often resulting in inconsistent formatting, missed breaking changes, and incorrect version bumps. ## Core Features & Use Cases - Commit Analysis & Categorization: Parses conventional commits, PR titles, and issue references, grouping changes into Added, Fixed, Changed, Breaking Changes, and other Keep a Changelog sections. - Semantic Versioning Suggestions: Detects breaking changes via BREAKING CHANGE footers and ! markers, then recommends the correct MAJOR, MINOR, or PATCH version bump. - Dual Output Formats: Produces both a developer-facing CHANGELOG.md and user-friendly release notes with highlights, contributors, and installation instructions. - Use Case: Before tagging v2.1.0, run this Skill against commits since the last release to generate a formatted changelog, draft GitHub release notes, and a migration guide for any breaking API changes. ## Quick Start Generate a changelog and release notes from all commits since the last git tag and suggest the next semantic version.

Frequently Asked Questions about changelog-writer

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

FAQPage Schema
How do I generate a changelog from git commits?▼

Run git log from the last tag to HEAD, parse conventional commit prefixes like feat and fix, then group entries into Keep a Changelog sections such as Added, Fixed, and Changed. Tools like conventional-changelog or git-cliff can automate this.

How to write release notes from conventional commits?▼

Map commit types to categories: feat becomes New Features, fix becomes Bug Fixes, and BREAKING CHANGE footers become Breaking Changes. Rewrite entries in user-friendly language, link issue numbers, and credit contributors.

What is the difference between a changelog and release notes?▼

A changelog is developer-facing with technical details, API changes, and migration guides following Keep a Changelog format. Release notes are user-facing, focusing on benefits, highlights, and upgrade instructions with less technical jargon.

How do I detect breaking changes in commit history?▼

Look for BREAKING CHANGE footers in commit messages, an exclamation mark after the type like feat!:, PRs labeled breaking-change, major dependency updates, and API endpoint or config format changes.

When should I bump major vs minor vs patch version?▼

Bump MAJOR for breaking or incompatible changes, MINOR for new backward-compatible features, and PATCH for bug fixes and security patches. Versions below 1.0.0 allow breaking changes in minor releases.

Can I automate changelog generation with git-cliff or conventional-changelog?▼

Yes. conventional-changelog -p angular -i CHANGELOG.md -s updates an existing changelog, while git-cliff --tag v2.1.0 generates one from scratch. Both parse conventional commits automatically.