gitlab-mr-review

Review GitLab merge request diffs and post inline comments.

Updated May 10, 2026
One-click install
npx skills add https://github.com/dthuy62/kollet-app --skill gitlab-mr-review-dthuy62
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitlab-mr-review
Source: https://github.com/dthuy62/kollet-app/tree/main/.claude/skills/gitlab-mr-review
Command: npx skills add https://github.com/dthuy62/kollet-app --skill gitlab-mr-review-dthuy62

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill removes the manual overhead of reviewing GitLab merge requests by fetching diffs, organizing change context, and turning findings into precise inline review comments.

Core Features & Use Cases

  • Merge Request Diff Retrieval: Pulls MR metadata, changed files, and version SHAs from a self-hosted GitLab instance.
  • Automated Review Workflow: Prepares review-ready context so an agent can assess bugs, security risks, performance issues, and error handling gaps.
  • Inline Comment Posting: Converts review findings into GitLab discussions positioned on the correct file and line.
  • Use Case: A maintainer can point the Skill at a merge request URL or project and let it gather the diff, review the changes, and publish actionable comments back to GitLab.

Quick Start

Ask this Skill to review a GitLab merge request by ID or URL and post inline comments on the relevant changed lines.

Frequently Asked Questions about gitlab-mr-review

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

FAQPage Schema
How do I automate code review on a self-hosted GitLab merge request?

To post inline code review comments on GitLab merge requests, you need to authenticate with GITLAB_URL and GITLAB_TOKEN credentials, which allow the API to retrieve MR versions, changes, and discussions for targeted feedback.

What is needed to authenticate API access for posting inline comments to GitLab MRs?

To post inline code review comments on GitLab merge requests, you need to authenticate with GITLAB_URL and GITLAB_TOKEN credentials, which allow the API to retrieve MR versions, changes, and discussions for targeted feedback.

Can I fetch merge request diffs and metadata from a private GitLab instance?

The automated review workflow prepares review-ready context by inspecting unified diffs fetched from the GitLab API, allowing an agent to assess bugs, security risks, performance issues, and error handling gaps in the changed files.

How does automated merge request review identify bugs and security risks?

Yes, you can target a specific merge request by providing its ID or URL to gather the diff, review the changes, and publish actionable discussions positioned on the correct file and line back to GitLab.

Does this approach support converting review findings into GitLab discussions on specific lines?

Yes, this approach converts review findings into GitLab discussions positioned on the correct file and line, turning automated analysis of merge request diffs into precise inline comments.