skills.rest
ORANGECRAB13
ORANGECRAB13COMMUNITY
Explore all skills by this author →
GitHub

changelog

Generate structured changelog files for significant PR commits.

Updated Apr 11, 2026
Search Tags:#automation#git#changelog#documentation#release#pr
One-click install
npx skills add https://github.com/ORANGECRAB13/vocareMVP --skill changelog-orangecrab13
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/ORANGECRAB13/vocareMVP/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/ORANGECRAB13/vocareMVP --skill changelog-orangecrab13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create changelog files for important commits in a PR by automatically generating standardized entries, reducing manual documentation effort.

Core Features & Use Cases

  • Automatic changelog generation: Scan commits on the current branch compared to main and generate appropriately named files in changelog/.
  • Selective logging: Skip changelogs for documentation-only, internal refactoring, test-only, or CI changes.
  • Flexible file naming: Produce files like {PR_NUMBER}.added.md or {PR_NUMBER}.changed.md to reflect the nature of changes.

Quick Start

Run the skill on a PR branch to generate changelog entries in changelog/ following the PR number conventions.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I automatically generate changelog entries for pull requests?▼

To automatically generate changelog entries, run the skill on a PR branch to compare commits with main and create structured markdown files in the changelog directory. It scans significant commits and produces standardized entries to reduce manual effort.

What naming convention is used for auto-generated PR changelog files?▼

Auto-generated PR changelog files use a PR_NUMBER.type.md naming convention, such as 1234.added.md or 1234.changed.md. This format reflects the specific nature of the changes made in the pull request.

Does the changelog generator skip documentation-only or CI-only commits?▼

Yes, the changelog generator skips documentation-only, CI-only, test-only, and internal refactoring commits. It selectively logs only significant changes to ensure the generated changelog remains focused on impactful modifications.

How do I create release notes from git commits without manual effort?▼

You can create release notes from git commits by running this skill during PR review. It compares the current branch with main, validates commit relevance, and automatically writes structured changelog entries for significant changes.

When should I not use an automated changelog generator for my repository?▼

You should not use an automated changelog generator if your project requires logging documentation-only updates, internal refactoring, or CI changes, as this skill is designed to skip those specific commit types and only log significant code changes.

Related Skills

Explore More Software Engineering Skills→
synaptiaisynaptiai
6

convention-enforcement

Validate git history and pull requests against repository-specific conventions.

Official
Intermediate
frostantfrostant
42

changelog-generator

Converts git commit history into categorized, ready-to-publish markdown release notes.

Community
Intermediate
mvandermeulenmvandermeulen
2

changelog-automation

Generate project changelogs and release notes from Conventional Commits history.

Community
Advanced
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate