Release Notes From Git Log Skill for Users and Developers (SKILL.md)

A SKILL.md that writes release notes from the commits between two tags, split into a plain-language section for users and a technical changelog for developers.

You get: User-facing notes, developer changelog in Keep a Changelog style and upgrade notes for each breaking change

More like this

Ready to use: no blanks to fill in.

The prompt

Installs to .agents/skills/release-notes-from-git-log-skill-for-users-and-developers-skill/

mkdir -p .agents/skills/release-notes-from-git-log-skill-for-users-and-developers-skill && curl -sL "https://prompts-gpt.com/prompts/release-notes-from-git-log-skill-for-users-and-developers-skill-md/raw" -o .agents/skills/release-notes-from-git-log-skill-for-users-and-developers-skill/SKILL.md
SKILL.md
Preview
---
name: release-notes-from-git-log-skill-for-users-and-developers-skill
description: "A SKILL.md that writes release notes from the commits between two tags, split into a plain-language section for users and a technical changelog for developers."
---

# Release Notes From Git Log Skill for Users and Developers (SKILL.md)

A SKILL.md that writes release notes from the commits between two tags, split into a plain-language section for users and a technical changelog for developers.

## Prompt

```
---
name: release-notes-from-git
description: Writes release notes and a changelog entry from git history between two tags or refs. Use when the user asks for release notes, a changelog, what changed since the last release, or a version announcement.
---

# Release notes from git

## Steps
1. Find the range. Default: the latest tag to HEAD (`git describe --tags --abbrev=0`). Confirm the range with the user if there are no tags.
2. Run `git log --no-merges --pretty=format:"%h %s" FROM..TO`, and read merged PR titles and bodies if the gh CLI is available.
3. Group commits: Breaking changes, New features, Improvements, Fixes, Security, Internal. Use Conventional Commit types when present; otherwise judge from the diff.
4. Drop noise: typo fixes, merge commits, version bumps, CI-only changes. List them as a count under Internal.
5. Read the diff for anything marked breaking or unclear. Never describe a change you have not confirmed.
6. Suggest the next version number using semantic versioning and say why.

## Output format
1. User-facing notes: plain language, benefit first, no commit hashes, under 200 words.
2. Developer changelog in Keep a Changelog style, with short hashes and PR numbers.
3. Upgrade notes for each breaking change: what breaks and the exact steps to migrate.
4. Suggested version number.

## Stop and ask
- The range contains more than 200 commits; ask whether to summarise by area.
- A commit message mentions a security fix; check whether it can be disclosed yet.

## Risks
Over-promising. Describe what shipped, not what was planned, and leave out features behind flags that are off.
```

## Usage Notes

Save as .claude/skills/release-notes-from-git/SKILL.md in a repo, or ~/.claude/skills/release-notes-from-git/SKILL.md for every project. Claude Code loads it when the description matches; the same file works in Codex, Cursor and Gemini CLI, which also read SKILL.md.

Tips and common edits

Save as .claude/skills/release-notes-from-git/SKILL.md in a repo, or ~/.claude/skills/release-notes-from-git/SKILL.md for every project. Claude Code loads it when the description matches; the same file works in Codex, Cursor and Gemini CLI, which also read SKILL.md.

Questions about this prompt

More in Coding

Test-First Bug Fix Skill: Reproduce, Fix, Prove (SKILL.md)

A SKILL.md that forces your coding agent to reproduce a bug with a failing test before changing code, apply the smallest fix, and prove it with the test suite.

Conventional Commit and PR Description Writer Skill (SKILL.md)

A ready-to-save SKILL.md that makes your coding agent write Conventional Commits messages and pull request descriptions from the staged diff, never from guesses.

Pre-Merge Code Review Checklist Skill (SKILL.md)

A save-ready SKILL.md that has your coding agent review a branch before merge: correctness, security, tests and migrations, with findings ranked by severity and no style nitpicks.

Brand Voice Guard Skill That Checks Drafts Against VOICE.md (SKILL.md)

A SKILL.md that makes Claude write and edit in your brand's voice: it reads a VOICE.md in the project, or builds one from samples, then checks every draft against it.

Meeting Notes to Decisions and Action Items Skill (SKILL.md)

A SKILL.md that turns any meeting transcript or rough notes into a decision log, owner-and-date action items, open questions and a ready-to-send recap email.

Spreadsheet and CSV Cleanup Report Skill (SKILL.md)

A SKILL.md that has your agent profile a messy CSV or spreadsheet, fix it in a copy with a script, and report every change so the cleaned data can be trusted.

Explain a Codebase Folder to a New Developer on Their First Day

Produces an onboarding guide for one folder of a codebase: what it does, how data moves through it, the files to read first and the traps a new developer should avoid.

Write a SKILL.md From a Workflow You Keep Repeating

Interviews you about a task you do over and over, then writes a complete, save-ready SKILL.md with a trigger description, steps, output format and stop conditions.

Characterization Tests Before a Refactor

Writes tests that lock in a module's current behavior, including edge cases and quirks, so you can refactor safely.

Codebase Tour for a Specific Task

Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.

Debug an Error From the Message and the Code Around It

Finds the most likely cause of an error from the message and the relevant code, ranks other possible causes, and gives the smallest fix plus a way to prove it worked.

Edge-Case Test Suite for One Function in Your Existing Test Framework

Writes tests for a single function that cover normal inputs, boundaries, bad input and error paths, in the test framework your project already uses.