mr-description

Generate GitLab merge request titles and descriptions from branch diffs.

4|Updated Feb 9, 2021

Search Tags:#diff analysis #workflow automation #conventional commits #breaking changes #release notes #gitlab #merge request

One-click install

npx skills add https://github.com/breengles/poor-man-OS-setup --skill mr-description

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: mr-description
Source: https://github.com/breengles/poor-man-OS-setup/tree/main/.claude/skills/mr-description
Command: npx skills add https://github.com/breengles/poor-man-OS-setup --skill mr-description

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of writing consistent, review-ready GitLab Merge Request titles and descriptions without manually analyzing branch changes.

Core Features & Use Cases

Automatic MR Title + Description Drafting: Analyzes the current branch versus main/master to produce a Conventional-Commits-style title and a structured description.
Breaking Change Detection (User-Facing Only): Detects and enumerates only user-facing breaking changes based on diff evidence and commit conventions, avoiding internal refactors.
Context-Aware Summaries: Uses merge base, commit messages, and changed-file diffs so the output reflects what reviewers actually need to know.

Quick Start

Use the mr-description skill on your current feature branch to generate a ready-to-paste GitLab Merge Request title and description based on differences from main or master.

Frequently Asked Questions about mr-description

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

FAQPage Schema

How do I generate GitLab merge request descriptions from commit history?▼

You can generate GitLab merge request descriptions by analyzing commits and diffs between your current branch and main/master. The skill collects merge-base context, scans commit metadata, and formats output to semantic-release and Conventional Commits structure.

Can I automatically detect breaking changes in my GitLab merge request diffs?▼

Yes, breaking changes are detected by scanning diffs and commit conventions. It specifically enumerates only user-facing breaking changes based on diff evidence, avoiding internal refactors that do not impact end users.

How to write Conventional Commits style titles for GitLab feature branches?▼

To write Conventional Commits titles for GitLab feature branches, the skill analyzes the differences from the main or master branch. It then produces a structured, review-ready title and description reflecting the actual changes.

Does this MR title generator work for both refactoring and bugfix branches?▼

Yes, this MR title generator works for feature development, refactors, and bugfixes. It uses changed-file diffs and commit messages to create context-aware summaries that accurately reflect what reviewers need to know.

What is the best way to format release notes for a GitLab merge request?▼

The best way to format release notes is to use semantic-release and Conventional Commits structures. The skill prepares release-quality merge request text by analyzing branch differences and calling out breaking changes.

Why does my generated MR summary include internal refactors as breaking changes?▼

Generated MR summaries should not include internal refactors as breaking changes. The skill specifically detects and enumerates only user-facing breaking changes based on diff evidence and commit conventions.