generate-release-notes

Generate categorized release notes by comparing two Git refs in a GitLab project.

37|4|Updated Apr 11, 2026

Search Tags:#changelog #mcp #release notes #gitlab #categorization #merge requests #git compare

One-click install

npx skills add https://github.com/jmrplens/gitlab-mcp-server --skill generate-release-notes-jmrplens

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: generate-release-notes
Source: https://github.com/jmrplens/gitlab-mcp-server/tree/main/.github/skills/generate-release-notes
Command: npx skills add https://github.com/jmrplens/gitlab-mcp-server --skill generate-release-notes-jmrplens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing release notes manually means digging through commit history and merged merge requests between two versions, then organizing everything into readable categories. This Skill automates that process by comparing two Git refs and producing polished, categorized release notes. ## Core Features & Use Cases - Ref Comparison: Compare any two Git refs (tags, branches, or commit SHAs) to gather commits, diffs, and merged merge requests via the GitLab MCP server. - Automatic Categorization: Classify changes into Breaking Changes, Features, Bug Fixes, Improvements, and Documentation using MR labels and conventional commit prefixes. - Formatted Output: Produce Markdown release notes with MR references, author attribution, contributor lists, and change statistics. - Use Case: Before tagging v1.1.0, compare it against v1.0.0 to instantly generate a changelog summarizing all merged MRs, contributors, and files changed for your release announcement. ## Quick Start Generate release notes for my GitLab project by comparing tag v1.0.0 to v1.1.0 and organize the changes by category.

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 between two Git tags in GitLab?▼

Compare the two tags using the GitLab repository compare action to gather commits and diffs, then list merged merge requests in that range. Categorize each change by MR labels or commit prefixes and format the results as Markdown release notes.

How to categorize commits for a changelog automatically?▼

Use conventional commit prefixes and MR labels as signals: feat maps to Features, fix to Bug Fixes, docs to Documentation, and perf or refactor to Improvements. Labels take precedence over prefixes, and breaking changes always appear first.

Can I compare branches or commits instead of tags?▼

Yes, any two valid Git refs work, including branches, commit SHAs, and tags. Common patterns include tag-to-tag, tag-to-branch, branch-to-branch, and commit-to-tag comparisons.

What GitLab MCP tools are needed for release notes generation?▼

The workflow uses the repository compare action to fetch commits and diffs, plus the merge request list action filtered to merged state. On the meta tool surface these are gitlab_repository and gitlab_merge_request; a generate_release_notes prompt is also available.

What happens when the commit range is too large?▼

If the range spans hundreds of commits, the returned data may be truncated and the tool will indicate this. Using specific tags rather than branch names keeps ranges bounded and produces reproducible release notes.