create-gitlab-mr

Create a feature branch, commit changes, push, and open a GitLab Merge Request.

9|2|Updated Apr 6, 2026

Search Tags:#automation #git #mcp #branching #commit message #gitlab #merge request

One-click install

npx skills add https://github.com/Dawn-Technology/aicelerate --skill create-gitlab-mr

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: create-gitlab-mr
Source: https://github.com/Dawn-Technology/aicelerate/tree/main/plugins/aimate/skills/create-gitlab-mr
Command: npx skills add https://github.com/Dawn-Technology/aicelerate --skill create-gitlab-mr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the manual steps of turning uncommitted local work into a pushed feature branch and a properly described GitLab Merge Request.

Core Features & Use Cases

Branch, commit, and push automation: Creates a feature branch from current changes, commits with a guideline-compliant message, and pushes to the remote.
GitLab Merge Request creation via MCP: Opens the Merge Request using the configured GitLab MCP server and dynamically targets the default branch rather than assuming main.
Clear error handling for auth issues: Detects unauthorized/expired token failures and asks the user to re-authenticate and retry.

Use case: You made several code changes locally and want them reviewed in GitLab as a Merge Request with a meaningful title/description and a correctly formatted commit message.

Quick Start

Ask to create a GitLab merge request for the current changes in your working directory using your configured GitLab MCP server.

Frequently Asked Questions about create-gitlab-mr

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

FAQPage Schema

How do I create a GitLab merge request from local uncommitted changes?▼

The merge request target branch is selected dynamically by inspecting the repository's default branch rather than assuming it is always 'main'. This ensures the MR is correctly targeted for your specific project setup.

What happens if my GitLab token is expired or unauthorized when pushing a branch?▼

If the GitLab MCP server returns an unauthorized or expired token error during merge request creation, the skill detects the failure and prompts you to re-authenticate before attempting to retry the push and MR operation.

Do I need a GitLab MCP server configured to open merge requests automatically?▼

Yes, you need a configured GitLab MCP server because the skill relies on it to open the merge request with a URL-encoded project id. Terminal-based Git inspection is also required for branch selection and commit generation.

Can I automate generating merge request descriptions from my current repository state?▼

Yes, you can automate generating merge request descriptions and titles from your current repository state. The skill transforms your uncommitted local work into a properly described GitLab merge request ready for review.