GitLab Code Review

Reviews GitLab merge requests for code quality, security, and performance issues.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/jwvdvuurst/CalculatorCollection --skill gitlab-code-review-jwvdvuurst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GitLab Code Review
Source: https://github.com/jwvdvuurst/CalculatorCollection/tree/main/skills/gitlab-code-review
Command: npx skills add https://github.com/jwvdvuurst/CalculatorCollection --skill gitlab-code-review-jwvdvuurst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reviewing merge requests is time-consuming and inconsistent, often missing security vulnerabilities, performance issues, or deviations from best practices before code gets merged. ## Core Features & Use Cases - Comprehensive MR Analysis: Fetches merge request diffs, commits, pipeline status, and existing discussions from GitLab to review only the changes introduced. - Structured Review Reports: Generates prioritized findings (Critical, Important, Suggestions) covering code quality, security, performance, testing, and documentation. - Direct MR Feedback: Optionally posts general comments or line-specific discussion threads back to the merge request after user confirmation. - Use Case: A developer types "review !42" and receives a full report on the MR's changes, including security concerns framed as constructive questions, plus the option to publish comments directly to GitLab. ## Quick Start Ask the assistant to review merge request !42 in your GitLab project and provide feedback on code quality and security.

Frequently Asked Questions about GitLab Code Review

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

FAQPage Schema
How do I review a GitLab merge request with AI?

Provide the merge request IID (e.g., "review !42") along with the project context. The skill fetches the MR details, diffs, commits, and pipeline status via gitlab-mcp tools, then generates a structured review report with prioritized findings.

How to review a merge request linked to a GitLab issue?

Provide the issue ID (e.g., "review #456"). The skill fetches the issue details, searches for related merge requests, asks you to confirm the correct one if multiple are found, and then proceeds with the standard review workflow.

Can the review comments be posted directly to the merge request?

Yes, but only after explicit user confirmation. The skill can add general comments via create_note or line-specific discussion threads via create_merge_request_thread using the diff_refs position data from the merge request.

Does this work with self-hosted GitLab instances?

Yes, the skill is configured for a self-hosted GitLab instance at https://gitlab-erp-pas.dedalus.lan. You need appropriate access credentials configured for that GitLab server through the gitlab-mcp server.

What are the limitations of automated merge request review?

The review only covers changes introduced in the merge request, not unrelated code. It depends on the gitlab-mcp server being available and may require pagination for MRs with many changed files. Feedback is advisory and framed as questions rather than definitive verdicts.