Verified:GitHub

do-mr-fix

Fetch and fix GitLab merge request comments with git and glab.

Updated Feb 17, 2026

Search Tags:#git #code review #gitlab #merge request #comment handling

One-click install

npx skills add https://github.com/purefunctions/my-agent-config --skill do-mr-fix

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: do-mr-fix
Source: https://github.com/purefunctions/my-agent-config/tree/main/skills/skills/do-mr-fix
Command: npx skills add https://github.com/purefunctions/my-agent-config --skill do-mr-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of addressing merge request comments in GitLab, saving time and reducing the risk of human error during code review cycles.

Core Features & Use Cases

Automated Comment Fetching: Fetch and categorize comments from a GitLab merge request.
Issue Fixing: Apply fixes to the codebase based on the reviewer comments.
Discussion Replying: Automatically reply to discussions with the fix status.
Use Case: Perfect for teams looking to streamline their GitLab code review process and ensure that every comment is addressed in a timely and consistent manner.

Quick Start

Run the 'do-mr-fix' skill with the MR identifier, such as: /do-mr-fix 42

Frequently Asked Questions about do-mr-fix

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

FAQPage Schema

How do I automate fixing GitLab merge request comments?▼

To automate fixing GitLab merge request comments, you can use a Skill that fetches reviewer feedback, applies codebase fixes, and replies to discussions automatically. It requires the git and glab command-line tools for MR operations.

Do I need glab to fetch and reply to GitLab merge request discussions?▼

Yes, you need glab to fetch and reply to GitLab merge request discussions. The tool relies on both the glab and git command-line utilities to resolve MR identifiers, handle branch checkout, and perform operations.

Can I automatically reply to code review discussions in GitLab?▼

You can automatically reply to code review discussions in GitLab by running an automated MR comment handling process. It analyzes discussions, applies fixes to the codebase, and posts the fix status directly back to the merge request threads.

What is the best way to handle branch checkout for a GitLab merge request?▼

The best way to handle branch checkout for a GitLab merge request is using an automated Skill that resolves MR identifiers and checks out branches. This ensures the correct code state is loaded before fetching comments and applying fixes.

What are the limitations of automating MR comment handling with glab?▼

Limitations of automating MR comment handling with glab include its strict dependency on the glab and git command-line tools. Without these installed, MR identifier resolution, branch checkout, and discussion analysis cannot function.