Verified:GitHub

mr-review

Reviews GitLab merge requests end-to-end and posts verdicts with Mattermost notifications.

1|Updated Sep 20, 2026

Search Tags:#automation #code review #worktree #gitlab #merge request #glab #mattermost

One-click install

npx skills add https://github.com/kdHyeok/MMP --skill mr-review-kdhyeok

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: mr-review
Source: https://github.com/kdHyeok/MMP/tree/main/skills/mr-review
Command: npx skills add https://github.com/kdHyeok/MMP --skill mr-review-kdhyeok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a GitLab merge request involves many manual steps: fetching the MR branch, reading the description and comments, analyzing the diff, deciding approve or hold, writing a structured review comment, and notifying the author. This Skill automates that entire workflow from a single MR link while enforcing review quality standards. ## Core Features & Use Cases - Isolated worktree review: Prepares a dedicated git worktree for the MR branch without touching your current working tree, then runs the diff and code analysis there. - Structured verdict workflow: Guides risk mapping, edge-case hunting, and falsification passes before recording an approve or hold verdict with mandatory reason categories like correctness, security, data, contract, and implementation. - Guarded publishing: Requires explicit user confirmation before posting the review comment to GitLab, then sends a Mattermost DM to the MR author with the review result. - Use Case: Paste an MR link and say "review this MR" — the Skill checks out the branch, reviews all changed files, asks for your approval, posts a formatted review comment, and DMs the author on Mattermost. ## Quick Start Review this merge request and post the verdict: https://gitlab.example.com/team/project/-/merge_requests/172

Frequently Asked Questions about mr-review

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

FAQPage Schema

How do I review a GitLab merge request automatically?▼

Provide the MR link and the Skill runs a prepare step that fetches the MR branch into a dedicated worktree, collects the description and latest author comments, then guides the diff review, verdict recording, comment posting, and Mattermost notification in order.

How to post a review comment on a GitLab MR with glab?▼

The Skill never calls glab mr note directly. It writes the review body to a file, records the verdict through the harness, asks for your explicit confirmation, then posts via the harness so section validation and state tracking are preserved.

Does this MR review workflow approve or merge the MR in GitLab?▼

No. The workflow only posts a review comment stating approve or hold. It never runs glab mr approve or glab mr merge; the human reviewer presses the GitLab approve button after reading the posted review.

Can I review an MR without changing my current git branch?▼

Yes. The prepare step creates a separate worktree under .claude/worktrees for the MR branch and fast-forwards it to the MR head. Your main repository branch and HEAD remain untouched throughout the review.

Why does the review comment get rejected before posting?▼

The harness rejects comments missing required sections or hold-reason category tags. Hold verdicts must include tagged findings with file locations, reproduction details, and fix guidance; unclassifiable findings belong in the non-blocking suggestions section.