generate-release-notes

Generate structured OWASP Juice Shop release notes from git tags, commits, and diffs.

Updated May 13, 2026

Search Tags:#changelog #github #owasp #release notes #git tags #categorization #templating

Ready to run

npx skills add https://github.com/tolonlo/FinalCiber --skill generate-release-notes-tolonlo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generate-release-notes
Source: https://github.com/tolonlo/FinalCiber/tree/main/.ai/skills/generate-release-notes
Command: npx skills add https://github.com/tolonlo/FinalCiber --skill generate-release-notes-tolonlo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the guesswork and inconsistency of writing or finishing release notes by deriving them from commit/PR history and mapping changes into the project’s established emoji-based structure.

Core Features & Use Cases

Release-note generation from repo history: Identifies the last tag, enumerates commits since that tag, and detects which parts of the codebase changed (runtime, frontend, challenges, configuration, i18n, etc.).
Iconography-driven categorization: Assigns changes to the correct release section using the project’s emoji conventions (e.g., Runtime, Challenges, Frontend/UI, Docker, Bugfixes, I18N, DevOps/Config).
Templates for major/minor/hotfix: Produces release notes that follow the correct formatting patterns, including disclaimers for breaking/policy-impacting changes.
Completion of existing drafts: Fills missing sections, standardizes kudos attribution, and ensures the final ordering and content coverage match the checklist.

Quick Start

Use the generate-release-notes skill to create a complete release-note draft for the current version by summarizing changes since the latest tag and formatting them with the correct section emojis and kudos lines.

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 git tags and commit history?▼

Generate release notes by analyzing git tags, enumerating commits since the last tag, and detecting changed codebase areas like runtime, frontend, and configuration. This process maps changes into structured sections using project-specific emoji conventions.

How does emoji iconography work for categorizing changelog sections?▼

Emoji iconography categorizes release notes by assigning changes to predefined sections like Runtime, Challenges, Frontend/UI, Docker, Bugfixes, I18N, and DevOps/Config. This ensures consistent formatting and visual structure across release drafts.

Can I use this to complete a partially written release draft?▼

Yes, you can complete existing release note drafts by filling missing sections, standardizing contributor kudos attribution using PR and commit references, and ensuring final content ordering matches the project checklist.

What is the best way to format breaking changes in a hotfix release?▼

Format breaking changes by applying specific templates for major, minor, and hotfix releases. These templates include required disclaimer rules for policy-impacting changes to ensure proper notification.

Does this work for OWASP Juice Shop release notes specifically?▼

Yes, this generates structured OWASP Juice Shop release notes by analyzing diffs across runtime, frontend, challenges, configuration, and i18n. It follows the project's specific emoji section iconography and kudos conventions.

How do I attribute contributor kudos in changelog entries?▼

Attribute contributor kudos by referencing pull requests and commit history within the generated release notes. This standardizes recognition lines and ensures proper attribution formatting across all entries.