ReviewGitLabMergeRequest

Fetch GitLab merge request details and diffs, then analyze code changes.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/Capplequoppe/agent-studio --skill reviewgitlabmergerequest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ReviewGitLabMergeRequest
Source: https://github.com/Capplequoppe/agent-studio/tree/main/.claude/skills/review-gitlab-mr
Command: npx skills add https://github.com/Capplequoppe/agent-studio --skill reviewgitlabmergerequest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and hooks (resource) components.

What problem does it solve?

This Skill streamlines the process of reviewing merge requests in GitLab, ensuring code quality and identifying potential issues before merging.

Core Features & Use Cases

  • Automated Context Fetching: Automatically retrieves merge request details and changed files using GitLab hooks.
  • Code Review Assistance: Provides tools and guidance for analyzing code quality, bugs, security, and performance.
  • Comment Integration: Facilitates adding inline and general comments directly to the merge request.
  • Use Case: A developer submits a merge request. This Skill fetches the MR details, checks out the branch, and guides the reviewer through analyzing the code changes and adding constructive feedback.

Quick Start

Use the ReviewGitLabMergeRequest skill to review merge request number 123.

Frequently Asked Questions about ReviewGitLabMergeRequest

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

FAQPage Schema
How do I review a GitLab merge request for code quality and security?

To review a GitLab merge request, the Skill fetches MR details and diffs, checks out the source branch, and analyzes code changes for quality, bugs, security, and performance. It guides you through the review and helps add constructive feedback.

What's the best way to add inline comments to a GitLab merge request during code review?

The best way to add inline comments is by using helper scripts that integrate directly with GitLab merge requests. The Skill facilitates adding both inline and general comments to the MR after analyzing the changed files.

Do I need glab and pnpm installed to review GitLab merge requests?

Yes, you need glab, git, and pnpm installed to review GitLab merge requests. These dependencies are strictly required for execution to fetch MR details, check out branches, and run the necessary analysis scripts.

How does automated context fetching work for GitLab code reviews?

Automated context fetching for GitLab code reviews works by retrieving merge request details and changed files using GitLab hooks. This automatically pulls the necessary diffs and metadata so you can analyze the code changes immediately.

Can I use this code review approach to identify bugs and performance issues before merging?

Yes, you can use this code review approach to identify bugs and performance issues before merging. The Skill analyzes code changes specifically for quality, security, bugs, and performance to ensure potential issues are caught early.

What are the limitations of using scripts and hooks to review GitLab merge requests?

A limitation of using scripts and hooks to review GitLab merge requests is the strict dependency on having git, glab, and pnpm properly configured in your environment. Execution will fail if these specific tools are missing.