Verified:GitHub

merge-request-review

Review GitLab merge requests using glab CLI and git diff for actionable findings.

Updated May 6, 2026

Search Tags:#code review #security review #test coverage #gitlab #merge request #git diff #glab

One-click install

npx skills add https://github.com/UnionStreetAI/unionstreet --skill merge-request-review-unionstreetai

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: merge-request-review
Source: https://github.com/UnionStreetAI/unionstreet/tree/main/plugins/gitlab/skills/merge-request-review
Command: npx skills add https://github.com/UnionStreetAI/unionstreet --skill merge-request-review-unionstreetai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing GitLab merge requests manually is time-consuming and error-prone, and reviewers often miss correctness bugs, security issues, and missing test coverage when scanning large diffs. ## Core Features & Use Cases - Merge Request Inspection: Uses `glab mr view` and `glab mr diff` to pull merge request context and changes directly from GitLab. - Local Diff Analysis: Combines remote MR data with local `git diff` output for a complete view of the changes under review. - High-Confidence Findings: Leads with correctness, security, and test-gap findings rather than stylistic nitpicks. - Use Case: A teammate opens a merge request touching authentication logic. Run this Skill to review the diff and surface a missing null check and an untested edge case before approval. ## Quick Start Review merge request 42 in the current GitLab repository and report high-confidence correctness, security, and test coverage findings.

Frequently Asked Questions about merge-request-review

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

FAQPage Schema

How do I review a GitLab merge request from the command line?▼

Use glab mr view to read the merge request description and metadata, then glab mr diff to fetch the changes. Combining these with local git diff gives full context for identifying correctness and security issues.

What should I look for when reviewing a merge request diff?▼

Focus on high-confidence findings: correctness bugs, security vulnerabilities, and gaps in test coverage. Leading with these categories keeps reviews actionable instead of drowning authors in style comments.

Does glab mr diff work without checking out the branch locally?▼

Yes, glab mr diff fetches the merge request changes directly from GitLab without a local checkout. Local git diff is used additionally when you have the branch checked out and want to compare against local state.

Why does glab fail to view a merge request in my repository?▼

glab requires an authenticated GitLab session and must run inside a repository with a GitLab remote. Verify authentication with glab auth status and confirm the remote URL points to your GitLab instance.