gitlab-mr

Automates GitLab merge request creation from commit history with configurable options.

4|Updated Oct 27, 2014
One-click install
npx skills add https://github.com/B-Galati/dotfiles --skill gitlab-mr-b-galati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitlab-mr
Source: https://github.com/B-Galati/dotfiles/tree/main/claude/skills/gitlab-mr
Command: npx skills add https://github.com/B-Galati/dotfiles --skill gitlab-mr-b-galati

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires glab, and includes references (resource) components.

What problem does it solve?

This skill automates the creation of GitLab merge requests by intelligently generating titles and descriptions from git commit messages, saving time and ensuring consistency.

Core Features & Use Cases

  • Automated MR Creation: Generates conventional titles and behavior-focused descriptions from commit history.
  • Customizable Options: Supports configurable assignees, labels, reviewers, and target branches.
  • Use Case: When you've completed a feature and want to create a merge request, this skill can automatically draft a clear title like "feat(expand-100): multiple improvements" and a concise description summarizing the changes from a user's perspective.

Quick Start

Use the gitlab-mr skill to create a merge request for the current branch targeting main.

Frequently Asked Questions about gitlab-mr

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

FAQPage Schema
How do I automate GitLab merge request creation from git commits?

You can automate GitLab merge request creation by using a tool that analyzes your git commits to generate conventional titles and behavior-focused descriptions, ensuring consistency across your project contributions.

Do I need glab CLI to create GitLab merge requests from commits?

Yes, the glab CLI is required to create GitLab merge requests from commits. The automation tool relies on this command-line interface to interact with your GitLab repository and submit the generated merge requests.

Can I set assignees, labels, and reviewers when creating a merge request from commits?

Yes, you can configure assignees, labels, reviewers, and target branches when creating a merge request from commits. This ensures the generated merge request includes all necessary metadata for your team's code review process.

How are merge request titles and descriptions generated from multiple commits?

Merge request titles and descriptions are generated by analyzing your git commit history to produce conventional titles and user-perspective behavior-focused descriptions, supporting both single and multiple commits.

Does this merge request automation support custom git commit conventions?

Yes, the merge request automation adheres to custom git commit conventions. It intelligently parses your commit messages to draft clear titles like "feat(expand-100): multiple improvements" and concise descriptions summarizing the changes.