gitlab-address-comments

Fetch and address unresolved review comments on GitLab merge requests using glab CLI.

Updated Feb 4, 2026

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

One-click install

npx skills add https://github.com/pchemguy/AISandbox --skill gitlab-address-comments-pchemguy

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: gitlab-address-comments
Source: https://github.com/pchemguy/AISandbox/tree/main/docs/AgentSkills/openai/skills/skills/.experimental/gitlab-address-comments
Command: npx skills add https://github.com/pchemguy/AISandbox --skill gitlab-address-comments-pchemguy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Reviewing and responding to merge request comments scattered across GitLab threads is tedious and easy to lose track of. This Skill pulls all unresolved discussions for the current branch's open MR into a structured JSON file, then guides triage and fixes so no reviewer feedback is missed. ## Core Features & Use Cases - Automated Discussion Fetching: Uses the `glab` CLI and GitLab API to locate the open MR for the current branch and export unresolved discussions, filtering out bot and system notes. - Batch Triage Workflow: Summarizes threads with author, file, and line context, then lets you select batches like `1,3,5-7`, `all`, or `top N` instead of handling comments one at a time. - Guided Fix Implementation: Shows full thread and code context for selected discussions, applies focused fixes, and runs relevant in-repo tests. - Use Case: A reviewer leaves eight comments on your feature branch MR. Run this Skill to fetch them, pick the top three, view the surrounding code, implement fixes, and report back which discussions were addressed. ## Quick Start Ask the assistant to fetch and help address the unresolved review comments on the open GitLab merge request for the current branch.

Frequently Asked Questions about gitlab-address-comments

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

FAQPage Schema

How do I fetch unresolved GitLab MR comments from the command line?▼

Run the fetch_comments.py script with the --open-comments flag to export unresolved discussions as JSON. It uses glab api to locate the open MR for your current branch and filters out bot and system notes automatically.

How to address GitLab merge request review comments in bulk?▼

Fetch unresolved discussions to a JSON file, review the numbered summary list, then select a batch such as 1,3,5-7, all, or top N. The workflow shows full thread and code context only for selected items before implementing fixes.

What version of glab CLI is required for GitLab MR discussions?▼

The glab CLI must be at least version 1.80.4, and authentication must succeed via glab auth login or the GITLAB_TOKEN environment variable. Verify setup by running glab auth status before fetching discussions.

Why does glab auth status fail when fetching MR comments?▼

Authentication fails when no valid GitLab token is configured or the session has expired. Run glab auth login or re-export GITLAB_TOKEN, then retry. If sandboxing blocks network calls, rerun with escalated permissions.

What happens if no open MR exists for the current branch?▼

The fetch script raises an error stating no open merge request was found for the source branch. In that case, provide the MR URL or IID manually, or confirm the branch has an associated open merge request.