Verified:GitHub

do-mr-review

Automate GitLab merge request reviews with inline comments and user confirmation.

Updated Feb 17, 2026

Search Tags:#code review #merge request #automated review #GitLab #technical assessment

One-click install

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

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of reviewing GitLab merge requests for correctness and technical defects, reducing manual effort and improving code quality.

Core Features & Use Cases

Automated Code Review: Review GitLab merge requests for bugs, security issues, and code quality.
Design Review Lens: Includes design review aspects for full, design, or maintainability reviews.
Tiered Risk Assessment: Applies different review levels based on maintainability risk (Tier 0-3).
Inline Comments: Post findings directly as inline comments on the merge request.
User Confirmation: Requires user confirmation before posting any comments.

Quick Start

Use the do-mr-review skill to review the merge request with ID 42.

Frequently Asked Questions about do-mr-review

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

FAQPage Schema

How do I automate code review for GitLab merge requests?▼

Automated GitLab merge request code review checks correctness, technical defects, and design issues, then posts inline comments directly on the merge request after user confirmation.

Can I apply tiered risk assessment to GitLab code reviews?▼

Yes, tiered risk assessment applies different review levels based on maintainability risk from Tier 0 to Tier 3, allowing design and maintainability reviews to scale with code complexity.

Does automated merge request review require user confirmation before posting?▼

Yes, automated merge request review requires explicit user confirmation before finalizing and posting any inline comments to the GitLab merge request.

What is the best way to check merge requests for technical defects and design issues?▼

The best way to check merge requests for technical defects and design issues is using an automated review lens that evaluates correctness and applies maintainability reviews based on risk tier.

Can I review a specific GitLab merge request by its ID?▼

Yes, you can review a specific GitLab merge request by providing its unique ID, which triggers the automated review process for that merge request.