glab-mr

Reviews GitLab Merge Requests using the glab CLI with structured findings.

1|Updated Mar 3, 2026

Search Tags:#git #code review #cli #diff #gitlab #merge request #glab

One-click install

npx skills add https://github.com/akhy/agent-skills --skill glab-mr-akhy

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: glab-mr
Source: https://github.com/akhy/agent-skills/tree/main/glab-mr
Command: npx skills add https://github.com/akhy/agent-skills --skill glab-mr-akhy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing GitLab Merge Requests thoroughly is time-consuming, and subtle issues like interaction bugs, silent regressions, and untested edge cases are easy to miss when scanning diffs alone. ## Core Features & Use Cases - End-to-End MR Review: Fetches MR metadata, checks out the branch, diffs changes, and reads changed files in full context using the glab CLI. - Multi-Level Issue Detection: Examines correctness, edge cases, validation, test coverage, breaking changes, and documentation gaps. - Structured Review Output: Produces a summary, per-file breakdown with severity indicators, and concrete issues with suggested fixes. - Use Case: A teammate asks you to review MR 42 before merging. The Skill checks out the branch, skips generated files like lockfiles and mocks, reads the handwritten changes in context, and reports a missing negative test plus a potential breaking change to a config key. ## Quick Start Ask the assistant to review GitLab MR 42 in the current repository using the glab CLI.

Frequently Asked Questions about glab-mr

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 the glab CLI to review a Merge Request locally: run glab mr show to fetch metadata, glab mr checkout to switch to the MR branch, and glab mr diff to inspect the changes. This Skill automates that sequence and adds structured analysis.

How to review a large GitLab MR with many generated files?▼

Identify handwritten versus generated files first, then exclude lockfiles, mocks, and protobuf outputs from the diff. You can run git diff origin/main...HEAD with path exclusions like ':(exclude)*.lock' to focus only on meaningful changes.

Does glab mr checkout work with uncommitted local changes?▼

Checking out an MR branch with uncommitted changes can mix your local work into the review context. The Skill warns you to stash or commit changes with git stash before proceeding with glab mr checkout.

What should a thorough code review of a merge request cover?▼

A thorough review covers functional correctness, edge cases like empty or disabled inputs, validation and contracts, test coverage including negative and combination tests, breaking changes to public interfaces, and documentation updates.

Why does glab mr list or checkout fail in my repository?▼

glab commands fail when the CLI is not authenticated or the GitLab remote is unreachable. Verify authentication with glab auth status and confirm the repository remote points to your GitLab instance before retrying.