add-changelog-entry

Parse recent diffs and append categorized changelog entries to UNRELEASED.md.

11|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/reporails/rules --skill add-changelog-entry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-changelog-entry
Source: https://github.com/reporails/rules/tree/main/.claude/skills/add-changelog-entry
Command: npx skills add https://github.com/reporails/rules --skill add-changelog-entry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates updating UNRELEASED.md with new changelog entries derived from recent diffs, reducing manual effort and error.

Core Features & Use Cases

  • Area-aware categorization: determines the affected repository area based on file paths (e.g., core/**/rule.md → [RULES], registry/ → [REGISTRY], schemas/ → [SCHEMAS], agents/ → [AGENTS], docs/ → [DOCS], CLAUDE.md, backbone.yml, .claude/, .reporails/ → [META]).
  • Descriptive entry generation: creates a concise, human-readable description (3-7 words) of the change.
  • Safe integration: appends to UNRELEASED.md under the appropriate [Category] header, creating the section if missing.

Quick Start

Run the tool to append a concise changelog entry to UNRELEASED.md based on recent diffs.

Frequently Asked Questions about add-changelog-entry

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

FAQPage Schema
How do I automatically generate changelog entries from git diffs?

You can automatically generate changelog entries from git diffs by parsing file paths from recent changes and appending a concise description to UNRELEASED.md, reducing manual effort and error in release workflows.

How does area-aware categorization work for repository changes?

Area-aware categorization works by parsing file paths from recent diffs to assign the correct repository area, such as mapping core/**/rule.md to [RULES] or registry/ to [REGISTRY], ensuring changes are organized correctly in the changelog.

What's the best way to keep an unreleased changelog updated during development?

The best way to keep an unreleased changelog updated is to append concise entries to UNRELEASED.md automatically after changes are made, creating missing category sections as needed so documentation stays current without manual intervention.

Does automated changelog generation work with custom repository directory structures?

Automated changelog generation works with custom repository directory structures by parsing specific file paths like schemas/ and agents/ to determine the affected area, then appending the generated entry under the appropriate category header in UNRELEASED.md.

Why are my manually written changelog entries inconsistent across different repository areas?

Manually written changelog entries become inconsistent due to human error in categorizing file paths and varying description lengths, whereas automated diff parsing assigns correct area tags and generates concise 3-7 word descriptions uniformly.