gitlab-mr

Automate GitLab Merge Request lifecycle with CI fixes and conflict resolution.

42|7|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/addxai/enterprise-harness-engineering --skill gitlab-mr-addxai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitlab-mr
Source: https://github.com/addxai/enterprise-harness-engineering/tree/main/skills/gitlab-mr
Command: npx skills add https://github.com/addxai/enterprise-harness-engineering --skill gitlab-mr-addxai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating and managing GitLab Merge Requests often leads to unmergeable MRs stuck due to missing required documentation, failing CI pipelines, or unresolved merge conflicts, wasting developer time and blocking code delivery.

Core Features & Use Cases

  • End-to-end MR lifecycle management: Automatically creates or updates MRs with required documentation blob links, pushes branches, and polls CI pipeline status.
  • CI failure remediation: Identifies failed pipeline jobs, provides targeted fixes for common issues like missing documentation or security scan failures, and retries jobs automatically.
  • Merge conflict resolution: Detects merge conflicts with the target branch, guides rebasing onto main, and force pushes to trigger new CI runs.
  • Use case: A developer finishing a feature branch for retry logic can use this skill to automatically generate the MR description with linked design docs, fix any failing CI checks, and resolve merge conflicts to get the MR ready for merge without manual tracking.

Quick Start

Use the gitlab-mr skill to submit your current feature branch for review and drive the resulting Merge Request to a fully mergeable state with all CI checks passing and no conflicts.

Frequently Asked Questions about gitlab-mr

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

FAQPage Schema
How do I automatically resolve merge conflicts in a GitLab merge request?

To resolve merge conflicts in a GitLab merge request, the skill detects conflicts with the target branch, guides rebasing onto main, and force pushes to trigger new CI pipeline runs automatically.

What's the best way to fix failing GitLab CI pipelines blocking a merge request?

Fixing failing GitLab CI pipelines involves identifying failed jobs, providing targeted fixes for missing documentation or security scan failures, and automatically retrying jobs to unblock the merge request.

Can I use glab CLI to manage the end-to-end merge request lifecycle on a custom GitLab instance?

Yes, you can use glab CLI with custom GitLab instances like gitlab.example.com to manage the end-to-end MR lifecycle, including branch review, description generation, and merge workflows.

How do I generate a GitLab merge request description with valid documentation blob links?

Generating a GitLab merge request description with valid blob links is automated by pushing branches and updating MRs to include required documentation references for merge validation.

Why does my GitLab merge request stay unmergeable even after passing CI checks?

A GitLab merge request stays unmergeable after passing CI checks if required documentation blob links are missing or unresolved merge conflicts with the target branch remain, requiring iterative validation.

Do I need to manually rebase my feature branch if a GitLab MR has conflicts with main?

No, you do not need to manually rebase; the skill detects merge conflicts with the target branch and guides rebasing onto main automatically to drive the MR to a fully mergeable state.