changelog

Generate a PR narrative and Keep-a-Changelog entry from a git diff and acceptance criteria.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/paulingham/.claude --skill changelog-paulingham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/paulingham/.claude/tree/main/skills/changelog
Command: npx skills add https://github.com/paulingham/.claude --skill changelog-paulingham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This capability closes the gap between code changes and human-readable documentation by automatically generating a PR narrative and a Keep-a-Changelog entry from the diff and the acceptance criteria.

Core Features & Use Cases

  • Generates a concise PR narrative suitable for reviewers who did not watch the build.
  • Appends a Keep-a-Changelog entry under the Unreleased section, mapping changes to Added/Changed/Fixed as appropriate.
  • Invoked from /harness:pr-creation after the Final Gate emits APPROVED, and usable standalone for release notes.

Quick Start

Invoke after a Final Gate approval to generate a PR narrative and append a changelog entry to CHANGELOG.md.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I automatically generate release notes from a git diff?

You can automatically generate release notes by reading the diff between origin/main and HEAD alongside acceptance criteria to format a narrative PR body and append a Keep-a-Changelog entry under the Unreleased section in CHANGELOG.md.

What is the best way to create a PR narrative for reviewers from code changes?

The best way to create a PR narrative is to process the branch diff and acceptance criteria, producing a concise human-readable summary suitable for reviewers who did not watch the build process unfold.

How do I append Keep-a-Changelog entries to CHANGELOG.md automatically?

You can append Keep-a-Changelog entries by analyzing the diff and acceptance criteria to map changes to Added, Changed, or Fixed categories, then writing the formatted entry directly under the Unreleased section of CHANGELOG.md.

Can I generate changelog entries standalone without a full deployment workflow?

Yes, you can use the capability standalone to generate release notes for the current branch, or invoke it from a PR creation workflow after a Final Gate emits an APPROVED status to document the finalized changes.

Does the changelog generation require acceptance criteria to map code changes?

Yes, the changelog generation reads both the git diff and the acceptance criteria to accurately format the PR narrative and map the modifications into the correct Keep-a-Changelog categories.

What git diff range is needed to generate PR narratives and changelog entries?

The generation process requires the diff between origin/main and HEAD to analyze the committed changes, read the acceptance criteria, and produce the corresponding PR narrative and changelog entry.