skills.rest
nimadorostkar
nimadorostkarCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

changelog

Create user-facing changelogs organized by impact with migration guidance.

25|3|Updated Jul 14, 2026
Search Tags:#changelog#versioning#documentation#communication#migration#release-notes
One-click install
npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill changelog-nimadorostkar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/nimadorostkar/Claude-Skills-collection/tree/main/skills/writing/changelog
Command: npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill changelog-nimadorostkar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the common issue of writing technical, developer-centric changelogs that fail to communicate value or breaking changes to end users.

Core Features & Use Cases

  • User-Centric Structuring: Organizes updates by impact (Added, Changed, Deprecated, Removed, Fixed) rather than by commit history.
  • Breaking Change Communication: Provides a framework for clearly documenting breaking changes and offering migration guidance.
  • Semantic Versioning Guidance: Helps determine correct version numbers based on the nature of the changes rather than the size of the diff.

Quick Start

Use the changelog skill to draft release notes for the current version by summarizing the provided pull requests and highlighting any breaking changes.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I write release notes that communicate breaking changes to users?▼

Release notes for software updates should be organized by user impact rather than commit history. Group updates into Added, Changed, Deprecated, Removed, and Fixed categories to ensure end users understand what affects them directly.

What is the best way to structure a changelog for semantic versioning compliance?▼

Changelog structuring for semantic versioning involves categorizing changes by impact rather than diff size. Breaking changes dictate a major version bump, new features a minor bump, and fixes a patch bump.

How do I create migration guidance for deprecated features in release notes?▼

To create migration guidance for deprecated features in release notes, document the specific removal path and provide actionable steps under a Deprecated or Removed section, ensuring users know how to transition their implementation before the feature is fully removed.

Can I generate user-facing changelogs from pull requests automatically?▼

Generating user-facing changelogs from pull requests involves summarizing the provided pull requests and filtering for user-facing impact. You highlight breaking changes and group the remaining updates into standardized professional documentation categories.

Why do developer-centric changelogs fail to communicate value to end users?▼

Developer-centric changelogs fail to communicate value because they list commit history rather than user impact. Structuring updates by what changed for the user and providing migration guidance ensures the documentation is professional and actionable.

Related Skills

Explore More Content & Communication Skills→
tamzitamzi

release-changelog

Generates stable Paperclip changelogs from Git commit history, GitHub pull requests, and Calab for versioning/release tracking.

Community
Advanced
smart-swimmingpoolsmart-swimmingpool
25

release-please

Automate GitHub releases with Conventional Commits versioning and firmware binary deployment.

Official
Advanced
vasilyu1983vasilyu1983
73

docs-codebase

Generate documentation templates for READMEs, ADRs, API docs, and changelogs.

Community
Intermediate
legioncodeinclegioncodeinc
72

changelog-release-notes-stinger

Create user-focused changelog entries and release notes from software changes.

Official
Advanced