skills.rest
Barbaros911
Barbaros911COMMUNITY
Explore all skills by this author →
GitHub

changelog-from-commits

Generate user-facing changelog entries from raw git log output.

Updated Aug 12, 2026
Search Tags:#changelog#versioning#documentation#markdown#commits#release notes#git log
One-click install
npx skills add https://github.com/Barbaros911/As-mine --skill changelog-from-commits-barbaros911
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-from-commits
Source: https://github.com/Barbaros911/As-mine/tree/main/.claude/skills/solo-skills/changelog-from-commits
Command: npx skills add https://github.com/Barbaros911/As-mine --skill changelog-from-commits-barbaros911

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing release notes from a pile of raw commits is tedious and error-prone: developers write commit messages for other developers, not for end users. This Skill converts raw git log output into a clean, user-facing CHANGELOG entry by grouping, translating, and filtering commits. ## Core Features & Use Cases - Commit Grouping: Sorts commits into Added, Changed/Fixed, and Internal buckets following the Keep a Changelog style. - Dev-speak to User-speak Translation: Rewrites technical commit messages (e.g., "fix: handle null in payment.processor") into plain user language (e.g., "Fixed a crash when applying coupons to gift cards"). - Noise Filtering: Drops typo fixes, CI tweaks, dependency bumps, and version bumps that users do not care about. - Use Case: You are cutting release v1.4.0 and run git log v1.3.0..HEAD. The Skill produces a formatted Markdown section with Added, Fixed, and Internal headings, ready to paste into CHANGELOG.md. ## Quick Start Ask the AI to generate a user-facing changelog entry for version v1.4.0 from all commits since the previous tag.

Frequently Asked Questions about changelog-from-commits

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

FAQPage Schema
How do I write release notes from git commits?▼

Run git log with a range like git log <prev-tag>..HEAD --no-merges, then group commits into Added, Changed/Fixed, and Internal buckets. Rewrite each user-visible change in one past-tense sentence from the user's perspective and drop internal noise.

What is the difference between a changelog and a commit log?▼

A commit log is written by developers for developers and includes refactors, dependency bumps, and CI tweaks. A changelog is written for end users and only describes visible changes in plain language, grouped by Added, Changed, and Fixed.

Which commits should be excluded from a changelog?▼

Exclude typo fixes, README tweaks, CI configuration changes, version bumps, and pure refactors with no user-visible behavior change. Collapse remaining internal work like dependency updates into a single summary line at the bottom.

When should I not generate a changelog from commits?▼

Skip it when the repository has no user-facing surface, such as internal libraries or scripts, where a raw commit log suffices. Also avoid ranges spanning months of work; split them into smaller releases first.

What format should a changelog entry follow?▼

Use a version heading with the release date, then Added, Changed, Fixed, and Internal subsections, skipping empty ones. Each bullet is one past-tense sentence written from the user's perspective, with links to docs for features needing more context.

Related Skills

Explore More Software Engineering Skills→
umputunumputun
439

last-tag

Identify commits since the latest Git tag and format them into a table.

Community
Intermediate
langston-barrettlangston-barrett

release

Automate Rust release workflows with Cargo, GitHub, and CI.

Community
Advanced
mkolb22mkolb22

Changelog Generation

Parse Git commit history into structured Markdown and JSON changelogs.

Community
Advanced
drgaciwdrgaciw

changelog-automation

Generate changelogs and release notes from Conventional Commits in CI/CD pipelines.

Community
Intermediate