gitlab-mr-review

Publish code-review findings as draft notes to GitLab MR diff lines.

2|Updated May 25, 2021

Search Tags:#automation #gitlab #code-review #merge-request #glab #draft-notes

One-click install

npx skills add https://github.com/kang8/.dotfiles --skill gitlab-mr-review-kang8

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: gitlab-mr-review
Source: https://github.com/kang8/.dotfiles/tree/main/claude/.claude/skills/gitlab-mr-review
Command: npx skills add https://github.com/kang8/.dotfiles --skill gitlab-mr-review-kang8

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill enables publishing code-review findings to a GitLab merge request as inline draft notes, consolidating feedback without immediately publishing comments, and ensuring each finding is tied to the correct diff line.

Core Features & Use Cases

Inline draft reviews: post findings as draft notes that accumulate until you publish.
Line-accurate mapping: attach each finding to the correct added/removed/context line in the MR.
MR discovery & publishing: automatically determine the MR from the current branch or explicitly provided MR, and optionally publish drafts in bulk.

Quick Start

Provide a JSON array of findings and run the skill to post draft notes to the GitLab MR.

Frequently Asked Questions about gitlab-mr-review

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

FAQPage Schema

How do I post code-review comments as draft notes to a GitLab merge request?▼

To post draft notes to a GitLab merge request, provide a JSON array of code-review findings and run the skill to attach each finding as an inline draft note to the correct diff line.

Can I bind code-review findings to specific diff lines in a GitLab MR?▼

Yes, you can bind code-review findings to specific diff lines in a GitLab MR. The skill maps each finding to the correct added, removed, or context line within the merge request diff.

Does this GitLab merge request review skill require the glab CLI?▼

Yes, this GitLab merge request review skill requires the glab CLI. It uses the glab CLI for all GitLab interactions to post draft notes and optionally publish them.

How do I automatically resolve a GitLab MR from the current branch for code review?▼

You can automatically resolve a GitLab MR from the current branch for code review. The skill determines the target merge request automatically from your current branch or an explicitly provided MR identifier.

What is the best way to accumulate code-review feedback before publishing to GitLab?▼

The best way to accumulate code-review feedback before publishing to GitLab is using inline draft notes. Draft notes consolidate feedback without immediately publishing comments, with an optional flag to publish in bulk.

What format do I need to provide code-review findings in to post them to a GitLab MR?▼

You need to provide code-review findings as a JSON array to post them to a GitLab MR. The skill processes this JSON input to map and attach each finding to the corresponding diff line as a draft note.