release-notes

Generates categorized release notes from Git commits, GitLab MRs, and Jira issues.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill release-notes-trigent-software-pvt-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/issues/skills/release-notes
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill release-notes-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing release notes manually requires digging through commit history, cross-referencing merge requests, and looking up Jira tickets one by one, which is slow and error-prone. This Skill automates that entire process by analyzing commits since the last tag and producing organized, categorized release notes. ## Core Features & Use Cases - Commit Analysis: Finds the latest Git tag and collects merge commits from origin/main, while excluding hotfixes already released via origin/master to avoid duplication. - Cross-Referencing: Looks up GitLab MR details and Jira issues (via MCP integrations) to extract accurate titles, types, and links for each change. - Smart Categorization: Groups changes into Features, Bugfixes, and Other Changes based on Jira issue types, with deduplication of MRs referencing the same ticket. - Use Case: Before tagging version 2.4.0, run this Skill to automatically produce a markdown changelog with linked Jira tickets, ready to paste into your release page. ## Quick Start Ask the AI to generate release notes for the upcoming release by analyzing commits since the last tag.

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 automatically?

This Skill finds the latest Git tag, collects merge commits since that tag, looks up the associated GitLab MRs and Jira issues, then formats everything into categorized markdown release notes with Features, Bugfixes, and Other Changes sections.

How to create a changelog from GitLab merge requests and Jira tickets?

The Skill extracts MR IIDs from merge commit messages, fetches MR details via GitLab MCP, then resolves Jira keys from MR titles, descriptions, or branch names. Each change is categorized by Jira issue type and linked in the final notes.

Does this release notes generator work with hotfix branches?

Yes, it handles hotfixes by comparing origin/master against origin/main. Commits already released as hotfixes on master are excluded from the new release notes, preventing duplicate entries across releases.

What integrations are required to generate release notes with Jira links?

You need the Atlassian MCP configured for Jira issue lookups, the GitLab MCP for merge request details, and Git access to fetch tags and the origin/main and origin/master branches.

Why are some merge requests missing Jira links in release notes?

An MR appears without a Jira link when no valid issue key is found in its title, description, or source branch name. In that case the notes fall back to showing the MR title with its branch name and MR number instead.