Verified:Website 𝕏@ProchazkaFilip GitHub

comments

Analyzes GitLab merge request discussion threads and proposes fixes for unresolved comments.

15|1|Updated Jan 3, 2026

Search Tags:#code review #comments #gitlab #merge request #triage #glab #discussion threads

One-click install

npx skills add https://github.com/fprochazka/claude-code-plugins --skill comments-fprochazka

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: comments
Source: https://github.com/fprochazka/claude-code-plugins/tree/main/plugins/glab/skills/comments
Command: npx skills add https://github.com/fprochazka/claude-code-plugins --skill comments-fprochazka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merge request review feedback accumulates across many discussion threads, and it is easy to miss unresolved comments or actionable feedback hidden in resolved threads. This Skill reads all dumped MR discussions and produces a plan for addressing every comment. ## Core Features & Use Cases - Unresolved Comment Triage: Reads each unresolved discussion thread and proposes whether to fix code, reply, or explain why no action is needed. - Resolved Comment Verification: Re-checks resolved threads to catch problems marked resolved that are not actually fixed, including feedback from AI reviewers. - Discussion Interaction: Replies to threads, resolves discussions, and adds diff notes on specific lines using the glab-discussion CLI. - Use Case: After a round of code review on a GitLab MR, run this Skill to get a per-thread action plan before implementing any changes. ## Quick Start Ask the assistant to review all unresolved and resolved comments on the current merge request and propose what to do about each one.

Frequently Asked Questions about comments

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

FAQPage Schema

How do I handle unresolved comments on a GitLab merge request?▼

Run this Skill to read all unresolved discussion threads dumped by glab-discussion. It analyzes each comment and proposes whether to fix the code, reply to the reviewer, or explain why no action is needed.

How to reply to a GitLab MR discussion from the command line?▼

Use glab-discussion write with the --reply-to flag followed by the discussion ID and a --body message. The discussion ID appears in the header of each dumped discussion file.

Can resolved GitLab comments still contain actionable feedback?▼

Yes. Some problems marked resolved are not actually fixed, and automated AI reviewers sometimes post comments that land in resolved threads. This Skill re-verifies resolved discussions to catch missed feedback.

Does this skill implement the fixes for MR comments automatically?▼

No. It only analyzes the discussion threads and proposes what to do about each comment. Implementation is a separate step performed after you review the proposals.

What tools are required to manage GitLab MR discussions with this skill?▼

It requires the glab-discussion CLI for reading and interacting with discussions, and the mr-state.py script from the plugin to gather comment context. The glab CLI binary must be installed separately.