Verified:GitHub

create-mr

Creates a GitLab merge request for the current branch with generated title and description.

Updated Jul 22, 2026

Search Tags:#automation #git #code review #mcp #gitlab #branch #merge request

One-click install

npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill create-mr-trigent-software-pvt-ltd

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: create-mr
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/issues/skills/create-mr
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill create-mr-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually creating GitLab merge requests requires gathering commit history, summarizing diffs, and writing descriptions by hand, which is repetitive and error-prone. This Skill automates the entire MR creation flow for the current branch. ## Core Features & Use Cases - Automatic Context Gathering: Detects the current branch, lists its commits, and inspects branch diffs to build an accurate MR summary. - Duplicate Detection: Checks whether an MR already exists for the source branch before creating a new one. - Structured Descriptions: Generates a formatted description with Summary, Changes, and Test plan sections, including ticket references parsed from branch names. - Use Case: After finishing a feature branch like PROJ-123-add-oauth, run the Skill to open a merge request against main with a complete description in seconds. ## Quick Start Create a GitLab merge request for my current branch targeting main.

Frequently Asked Questions about create-mr

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

FAQPage Schema

How do I create a GitLab merge request from the command line?▼

Run this Skill on your feature branch and it detects the current branch with git, gathers commits and diffs via the GitLab MCP tools, then calls create_merge_request with a generated title and description. You can optionally pass a target branch as an argument.

How to generate a merge request description automatically?▼

The Skill builds the description from your branch's commits and diff summary, formatting it into Summary, Changes, and Test plan sections. It also pulls ticket references like PROJ-123 from the branch name when present.

What happens if a merge request already exists for my branch?▼

The Skill checks for an existing MR using get_merge_request before creating one. If found, it reports the existing MR URL and asks whether you want to update it instead of creating a duplicate.

Can I specify a target branch other than main?▼

Yes, pass the target branch as an argument when invoking the Skill. Without an argument, it defaults to the repository's main branch, typically main or dev.

What tools does this Skill need to create a merge request?▼

It requires the GitLab MCP server tools (create_merge_request, get_merge_request, list_commits, get_branch_diffs, get_project) plus Bash access for git commands. Without the GitLab MCP connection, MR creation cannot complete.