mr-review

Review GitLab Merge Requests for correctness, security, and performance issues.

4|Updated Feb 9, 2021

Search Tags:#testing #static analysis #code review #security #edge cases #gitlab #merge request

One-click install

npx skills add https://github.com/breengles/poor-man-OS-setup --skill mr-review-breengles

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: mr-review
Source: https://github.com/breengles/poor-man-OS-setup/tree/main/.claude/skills/mr-review
Command: npx skills add https://github.com/breengles/poor-man-OS-setup --skill mr-review-breengles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you catch correctness bugs, security issues, edge-case failures, and code-quality problems early by reviewing a GitLab Merge Request thoroughly against the base branch.

Core Features & Use Cases

Adversarial diff review with full-context reading: Review changed files using their full current versions, not just the patch, to avoid missing invariants and call-site behavior.
Verification through building, testing, and smoke runs: Run compilation, type checking, linting, and tests when available, and perform realistic invocations for affected executables.
Structured, severity-based findings: Produce blockers, majors, minors, and nits with concrete file:line citations and actionable fixes, plus explicit edge-case coverage checks.

Quick Start

Provide the Merge Request URL (or IID) to review, and then request a verdict with cited, severity-labeled issues and any commands it can run.

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 for security vulnerabilities and edge cases?▼

You can review a GitLab merge request by providing the URL or IID to trigger an adversarial review that identifies security vulnerabilities, edge-case failures, and correctness defects before merge. It reads full file versions and relevant callers to analyze behavioral boundaries.

Can I perform static analysis on a GitLab merge request to catch correctness defects before merging?▼

Static analysis on a GitLab merge request helps catch correctness defects by determining the correct base branch, reading full file versions, and attempting build, typecheck, and lint verification. This process produces file:line findings with severity labels and concrete fixes.

What is the best way to run tests and smoke checks on a GitLab merge request diff?▼

The best way to run tests on a GitLab merge request diff is to use a review process that attempts compilation, type checking, linting, and realistic smoke runs for affected executables when feasible. This verifies behavioral boundaries and outputs structured, severity-based findings.

Does adversarial code review work with multi-file merge requests spanning multiple changed files?▼

Adversarial code review works with multi-file merge requests by applying diff-to-context reasoning across all changed files. It reads full current file versions rather than just the patch to avoid missing invariants and call-site behavior.

How do I get structured code review findings with severity levels for my GitLab merge request?▼

To get structured code review findings with severity levels, provide the merge request URL to an adversarial review process. It outputs blockers, majors, minors, and nits with concrete file:line citations and actionable fixes for identified code-quality problems.