BestPromptFinder

Release Notes from Git History

Quality, usefulness and confidence are AI evaluations out of 100 — not user ratings. Community results come from visitors' "worked / didn't work" votes below. How scoring works →

The prompt

Draft release notes for [version] covering [previous tag, e.g. v1.4.0]..[HEAD or new tag]. Gather facts first (read-only): - git log [from]..[to] --no-merges --pretty=format:"%h %s%n%b" - Merged PR titles and descriptions if available, e.g. gh pr list --state merged --search "merged:>=[YYYY-MM-DD]" --limit 200 - The diff for anything that looks breaking: migrations, config, public API, CLI flags. Then write notes for [audience: end users / API consumers / internal team]: 1. Highlights — 2–4 user-visible changes in plain language, most important first. 2. Breaking changes — what changed, who is affected, exact upgrade steps. If none, say "None". 3. New features, Improvements, Bug fixes — one line each, phrased as the user benefit, with the PR number or short commit hash. 4. Deprecations and security fixes, if any. 5. Skip internal-only work (CI, refactors, tests, dependency bumps with no user impact) unless I ask for a full changelog. Rules: every line must trace to a commit or PR — don't invent features or impact. Put commits you couldn't classify in a separate "Needs review" list. Output Markdown ready to paste into [CHANGELOG.md / the GitHub release]. Don't create tags, push, or publish.

Why this prompt

• Hand-picked, editorially reviewed prompt
• Written for Claude Code, Cursor

Source

Created by BestPromptFinder — editorial prompt, not user-generated. See our content & source policy.

Related Documentation prompts