HomeCasa Prompts

Changelog and release notes from a list of commits

Turn a list of commits or PRs into a Keep a Changelog entry, a SemVer version proposal, breaking changes with a migration guide and release notes your users can actually read. Designed for ChatGPT, Claude, Gemini and Microsoft Copilot. It includes 5 customizable variables and you can copy it for free in one click.

Beginner · Text · Pending editorial review

Designed for:

Prompt

Act as a release manager who writes accurate changelogs and readable release notes.

Context:
- Product or library: {{product}}
- Previous version and change range: {{range}}
- List of merged commits or PRs:
```
{{commits}}
```
- Audience for the notes: {{audience}}
- Output format: {{format}}

Deliverables:
1. Classify each commit as Added, Changed, Deprecated, Removed, Fixed or Security. Drop internal changes with no user impact (chore, ci, formatting) and list them separately.
2. A proposed version number under SemVer (major, minor or patch) with reasoning.
3. The changelog entry in the requested format, with the date [FILL IN: release date] and links to PRs where they appear.
4. A highlighted breaking changes section: what stops working, who is affected and a step-by-step migration guide with before/after code.
5. A version for the stated audience: 3-6 highlights explained by their benefit, in plain language if they are end users.
6. A list of ambiguous commits that need confirmation.

Constraints:
- Do not invent features or details that cannot be inferred from the commits. If a message is unclear, ask me or mark it [FILL IN].
- Write every line from the user's point of view, not the internal code's.
- If the previous version or the audience is missing, ask me first.

Format: Markdown ready to paste into CHANGELOG.md or the release page.

How to use it

Get the list with git log v1.4.0..HEAD --oneline or from the PRs merged since the last release. Check the proposed version and the breaking changes section before publishing.

Usage example

Product: JavaScript form validation library · Range: v2.3.1 to main · Audience: developers · Format: Keep a Changelog.

Sample output

Assuming a git log that includes, among others, a credit notes endpoint, a VAT rounding fix and the renaming of customer_id…

2. Proposed version

2.0.0 (major): renaming a response field breaks existing clients, even though the other changes would be minor and patch.

3. CHANGELOG entry

[2.0.0] – [FILL IN: release date]

Added

  • POST /credit-notes endpoint to issue credit notes against an existing invoice (#212).

Changed

  • BREAKING: the customer_id field is now client_id in every response (#219).

Fixed

  • The tax-inclusive total no longer differs by one cent from the sum of lines on invoices with many lines (#215).

4. Breaking changes and migration

Who is affected: any integration that reads customer_id.

Before: const id = invoice.customer_id;

After: const id = invoice.client_id;

6. Ambiguous commits

  • a3f9c1e wip validation — does it change what data the API accepts? [FILL IN]
  • 7be20d4 update deps — any security update that belongs under Security?

Internal changes (chore, ci, formatting) have been left out of the notes…

Key facts

Category
Programming & development · Documentation
Output type
Text
Level
Beginner
Designed for
ChatGPT, Claude, Gemini and Microsoft Copilot
Verified in
Pending editorial verification
Variables
Product or library, Previous version and range, Commits or PRs, Audience and Format
Language
English
Price
Free, no sign-up
Updated
Nov 7, 2026

Frequently asked questions

When should I bump the major version?

Under SemVer, when a change breaks compatibility with the public API. New backward-compatible features bump the minor version and bug fixes bump the patch.

What is the difference between a changelog and release notes?

A changelog is a complete technical record of changes. Release notes pick the most relevant items and explain their benefit for that release’s audience.

What is this prompt for?

Turn a list of commits or PRs into a Keep a Changelog entry, a SemVer version proposal, breaking changes with a migration guide and release notes your users can actually read.

Which AI tools does it work with?

It is designed for ChatGPT, Claude, Gemini and Microsoft Copilot. We have not verified it in these tools yet, so results may vary between them.

How do I customize the prompt?

Click “Customize” and fill in the variables (Product or library, Previous version and range, Commits or PRs, Audience and Format). The text updates instantly and you can then copy it in one click. Values are stored only in your browser.

Do I need experience to use it?

No. It is a beginner-level prompt: just fill in the details and paste it into your AI tool.

Is this prompt free?

Yes. Every HomeCasa Prompts prompt is free, with no sign-up or subscription. You can also use them in professional projects.

Can I trust the AI output?

Treat it as a high-quality draft: always check data, figures and important claims before publishing or making decisions.

Related prompts