release-notes

Generate release notes from Git commit logs between specified tags.

3|2|Updated Aug 31, 2025
One-click install
npx skills add https://github.com/donggyun112/ai-librarian --skill release-notes-donggyun112
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/donggyun112/ai-librarian/tree/main/.claude/skills/release-notes
Command: npx skills add https://github.com/donggyun112/ai-librarian --skill release-notes-donggyun112

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of user-friendly release notes by analyzing commit history, saving development teams significant time and effort in documentation.

Core Features & Use Cases

  • Commit Analysis: Gathers and processes commit messages from specified Git tags across multiple submodules (Backend, Frontend, Agent).
  • Categorization & Summarization: Groups commits into meaningful categories and transforms technical details into easily understandable descriptions.
  • Use Case: After a development sprint, provide the start and end Git tags (e.g., v1.0.17 and v1.0.18) to generate a polished release note detailing all significant changes for the next deployment.

Quick Start

Generate release notes by providing the start and end Git tags, for example, "v1.0.17 v1.0.18".

Frequently Asked Questions about release-notes

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

FAQPage Schema
How do I generate release notes from git commits between tags?

To generate release notes from git commits, provide the start and end Git tags. The tool analyzes the commit history between those tags, filters out noise, categorizes the changes, and formats the output into a polished summary.

What is the best way to automate changelog generation for multiple submodules?

Automating changelog generation for multiple submodules is done by analyzing commit logs across specified repositories like Backend, Frontend, and Agent, grouping technical commits into meaningful categories to communicate updates clearly.

Can I use git tags to categorize commit history for a deployment release?

Yes, you can use git tags to categorize commit history for a deployment release. By specifying start and end tags, the system processes commit messages to filter noise and create categorized release documentation.

Does release notes generation work with monorepos containing Backend, Frontend, and Agent submodules?

Release notes generation works with monorepos containing multiple submodules. It specifically supports analyzing commit logs across ICJC-Backend, ICJC-Frontend, and ICJC-Agent repositories to aggregate changes into a single output.

How are technical commit messages transformed into user-friendly release documentation?

Technical commit messages are transformed into user-friendly release documentation by filtering out noise and grouping commits into meaningful categories, turning detailed development logs into easily understandable descriptions of updates.