skills.rest
wendeus0
wendeus0COMMUNITY
Explore all skills by this author →
GitHub

changelog-entry

Generate a SemVer-compliant CHANGELOG entry from REPORT.md and branch diff.

Updated Aug 27, 2026
Search Tags:#changelog#documentation#semver#release-management#git-diff#report-md
One-click install
npx skills add https://github.com/wendeus0/AI-dotfiles --skill changelog-entry-wendeus0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-entry
Source: https://github.com/wendeus0/AI-dotfiles/tree/main/core/skills/changelog-entry
Command: npx skills add https://github.com/wendeus0/AI-dotfiles --skill changelog-entry-wendeus0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produces a user-facing CHANGELOG entry by extracting changes from a feature's REPORT.md and the branch diff, ensuring accurate release notes without developer-only jargon.

Core Features & Use Cases

  • Reads REPORT.md and the diff to identify changes that affect the user.
  • Classifies changes into SemVer categories (Added, Changed, Fixed, Removed) and formats them for a CHANGELOG.
  • Integrates with existing CHANGELOG.md while preserving the project's release narrative.

Quick Start

Run the changelog-entry skill against the current feature's REPORT.md and the corresponding git diff to generate a new CHANGELOG entry.

Frequently Asked Questions about changelog-entry

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

FAQPage Schema
How do I generate a changelog entry from a git diff automatically?▼

A SemVer-compliant changelog entry classifies changes into Added, Changed, Fixed, or Removed categories. It extracts user-facing modifications from the branch diff and REPORT.md, excluding developer-only jargon to ensure clear release notes.

Can I use a REPORT.md file to create user-facing release notes?▼

Yes, generating user-facing release notes from a REPORT.md file works by extracting changes that affect the user and filtering out developer-only jargon. The resulting entry integrates with your existing CHANGELOG.md while preserving the project's release narrative.

What's the best way to classify git changes into SemVer categories for a CHANGELOG?▼

The best way to classify git changes into SemVer categories for a CHANGELOG is to analyze the branch diff alongside REPORT.md. This automatically categorizes modifications into Added, Changed, Fixed, or Removed sections formatted for release preparation.

Does this changelog generation approach work without developer-only jargon in the output?▼

Yes, this changelog generation approach works without developer-only jargon by reading the branch diff and REPORT.md to extract only user-facing changes. It formats these changes into SemVer categories, ensuring the final CHANGELOG.md entry is accessible to users.

How do I append new release entries to an existing CHANGELOG.md file?▼

You can append new release entries to an existing CHANGELOG.md file by generating a formatted entry from your feature's REPORT.md and branch diff. This new entry is classified into SemVer categories and integrates seamlessly with your project's release narrative.

Related Skills

Explore More Software Engineering Skills→
yellow-seedyellow-seed

code-review

Identify and summarize differences between the current Git branch and its remote base branch.

Community
Basic
deinsoftwaredeinsoftware
125

swpm-release

Bump SWPM versions in package.json and update CHANGELOG.md from commits.

Official
Advanced
voidrotvoidrot

github-release

Automate GitHub release workflows with version bumps, changelogs, and PRs.

Community
Advanced
Arry8Arry8
1

changelog-generator

Parse Git history to generate Markdown changelogs in Keep a Changelog format.

Community
Intermediate