generate-release-notes

Generate release notes from Git commits and diffs since the latest tag.

Updated May 14, 2026

Search Tags:#changelog #versioning #github #release notes #git diff #contributor kudos #formatting automation

Ready to run

npx skills add https://github.com/VitorM147/juice-shop-private --skill generate-release-notes-vitorm147

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generate-release-notes
Source: https://github.com/VitorM147/juice-shop-private/tree/main/.ai/skills/generate-release-notes
Command: npx skills add https://github.com/VitorM147/juice-shop-private --skill generate-release-notes-vitorm147

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the time-consuming guesswork of writing release notes by automatically compiling changes since the last tag and formatting them into the project’s established iconography and sections.

Core Features & Use Cases

Release diff harvesting: Pulls commit lists, contributor signals, and targeted file diffs (runtime, UI, i18n, challenges, configuration) between the latest release tag and the current HEAD.
Categorization with iconography: Maps changes into the correct emoji-based sections (e.g., Runtime, Challenges, UI/Frontend, Docker, Bugfixes) and applies status markers like ⚡/⚠️/📜 where relevant.
Consistent release-note output: Produces notes in the expected bullet structure, includes kudos attribution, and ensures disclaimers and section order match the checklist templates.

Quick Start

Ask the AI to generate release notes for the juice-shop-private repository using the last Git tag as the baseline and the project’s section emoji conventions.

Frequently Asked Questions about generate-release-notes

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

FAQPage Schema

How do I generate release notes from a git diff automatically?▼

Generate release notes by harvesting commits and targeted file diffs since the latest Git tag, then mapping changes into structured sections with emoji-based categorization and contributor attribution.

How do I format changelog entries with emoji categories for major and minor releases?▼

Format changelog entries by mapping changes into correct emoji-based sections like Runtime, Challenges, UI/Frontend, Docker, and Bugfixes, applying status markers like ⚡/⚠️/📜 for major, minor, and hotfix releases.

Can I automate contributor kudos attribution when drafting GitHub release notes?▼

Yes, you can automate contributor kudos attribution by pulling contributor signals and commit lists between the latest release tag and HEAD, ensuring kudos are accurately assigned in the final release-note output.

Does this release notes generator support categorizing i18n and DevOps configuration changes?▼

Yes, this release notes generator supports categorizing i18n and DevOps configuration changes by applying targeted file comparisons that map updates directly into the correct template-consistent sections.

What is the best way to add disclaimers for breaking changes and policy updates in release notes?▼

The best way to add disclaimers for breaking changes and policy updates is through automated template-consistent formatting that applies specific disclaimer rules to relevant items during the release-note generation process.

When should I not use automated release notes generation for hotfix releases?▼

You should not use automated release notes generation when your hotfix changes span highly unconventional areas outside runtime, frontend/UI, challenges, configuration/DevOps, i18n, and policy, as the categorization relies on these defined scopes.