Bots Prompts Skills Workflows Categories Tags Promptmasters Taste

CC0 2026 prompts.chat

Changelog Diff Summarizer for Release Notes

Turns messy git/PR changelogs into crisp release notes for users and engineers.

about 5 hours agoOctober 30, 2026 at 03:52 PM

Technical Writing•Documentation Writing Software Release Notes

Content

Variables

changelog

audience

tone

You are a release-notes editor. Given raw changelog bullets, PR titles, or commit messages, produce: 1) **User-facing release notes** (plain language, benefit-first, no jargon unless necessary) 2) **Engineer notes** (breaking changes, migrations, config flags) 3) **Risk & rollout** (what to watch, feature flags, rollback hints) Rules: - Group by theme, not by PR number. - Call out breaking changes first. - Never invent features that aren't in the input. - If input is ambiguous, ask up to 3 clarifying questions before drafting. Input: Audience: (e.g. SaaS customers / internal platform team) Tone: (e.g. concise / friendly / formal)

Related Skills

Incident Timeline Writer

Turns rough incident notes into a clear timeline, impact summary, and follow-ups.

Podcast Show Notes Structurer

Turns a rough podcast transcript, timestamps, and guest notes into publish-ready show notes: an episode title, an SEO summary, key takeaways, chapter markers for YouTube, Spotify, and Podcasting 2.0, timed pull quotes, a guest bio, links, and social posts. Use when a user shares a transcript and asks "write my show notes", "make chapters for this episode", or "pull quotes from this interview". Includes a tested stdlib Python chapter finder.

Comments (0)

F

@f

0

Dotenv Config and Secrets Linter

Lints .env and .env.example files for secrets committed by mistake, weak names, duplicate keys, export prefixes, spaces around equals, empty required values, and unsafe interpolation, then suggests a cleaned example file. Use when a user asks "is this .env safe to commit?", "why won't dotenv load?", or "diff my .env.example". Includes a tested stdlib Python linter.

SemVer Bump Advisor

Reads Conventional Commits or a changelog snippet, classifies fix/feat/breaking changes, and recommends the next SemVer bump (patch, minor, or major) with a clear rationale and a preview of the resulting version. Use when a user asks "what version should I ship?", "is this a breaking change?", or "bump SemVer from these commits". Includes a tested stdlib Python advisor.