gitlab-mr-review

Review GitLab Merge Requests with inline findings and structured comments.

9|2|Updated Apr 6, 2026

Search Tags:#code quality #diff analysis #architecture #security #gitlab #inline comments #merge request review

One-click install

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

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps reviewers deliver thorough, evidence-based feedback on GitLab Merge Requests while reducing duplicated discussion and missed issues.

Core Features & Use Cases

Structured MR review workflow: Verifies capabilities, fetches MR metadata and discussions, checks out an isolated worktree, and traces the diff with codebase context.
Evidence-grounded findings: Classifies issues across security, correctness/logic, architecture/maintainability, and scope/consistency, using a strict finding schema tied to diff evidence.
Actionable review output: Presents a grouped findings report and then (only with user confirmation) drafts and publishes inline review comments, or drives approve/request-changes flows.

Quick Start

Ask the agent to review a specific GitLab Merge Request URL and wait for the findings report before it posts any comments.

Frequently Asked Questions about gitlab-mr-review

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

FAQPage Schema

How do I automate GitLab merge request code review with inline comments?▼

GitLab merge request review can be automated by fetching MR metadata, checking out an isolated worktree, analyzing the diff, and publishing line-positioned inline comments directly to the merge request.

What does diff analysis cover when reviewing a GitLab merge request for code quality?▼

Diff analysis for code quality covers security, correctness, logic, architecture, and maintainability, classifying issues using a strict finding schema tied to diff evidence for added, modified, or deleted lines.

How do I post review comments to GitLab merge requests programmatically?▼

You can post review comments to GitLab merge requests programmatically by using GraphQL read/write review operations to publish line-positioned findings, but only after presenting a grouped findings report and receiving user confirmation.

Do I need GitLab MCP capabilities to perform automated merge request reviews?▼

Yes, you need GitLab MCP capabilities for GraphQL read/write review operations and access to diffs with base/start/head SHA positioning to perform deterministic worktree-based code inspection and inline commenting.

When should I use an isolated worktree for merge request code review?▼

You should use an isolated worktree for merge request code review when you need to trace the full diff with codebase context and perform deterministic code inspection without affecting your local working directory.