Verified:GitHub

gitlab-mr-discussion-threads

Replies to GitLab merge request code review threads via glab API calls.

Updated Nov 18, 2025

Search Tags:#code review #gitlab #merge requests #glab #threaded replies #discussion threads

One-click install

npx skills add https://github.com/cajias/claude-skills --skill gitlab-mr-discussion-threads

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you respond to GitLab merge request review feedback in the correct threaded discussion instead of accidentally posting a top-level comment.

Core Features & Use Cases

Threaded Replies: Find the right discussion ID and post a reply directly inside an existing code review thread.
Comment Management: Delete your own discussion notes when you need to clean up or correct a response.
Review Workflow Support: Handle common MR review tasks such as responding to inline feedback, tracking unresolved discussions, and working with paginated discussion lists.

Quick Start

Help me reply to a specific GitLab merge request discussion thread using glab by finding the discussion ID and posting a nested response.

Frequently Asked Questions about gitlab-mr-discussion-threads

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

FAQPage Schema

How do I reply to a specific GitLab merge request discussion thread using glab?▼

To reply to a GitLab merge request discussion thread using glab, you must locate the target discussion ID from the paginated list and use the API to post a nested response directly inside that thread.

Why are my glab merge request responses posting as top-level comments instead of threaded replies?▼

Your glab responses post as top-level comments when the specific discussion ID is not targeted. You must locate the discussion ID and use the API call to post a nested response within the existing thread.

Can I delete my own notes from a GitLab merge request code review thread?▼

Yes, you can delete your own notes from a GitLab merge request code review thread by handling the specific note ID through glab API calls to clean up or correct your response.

What is required to manage GitLab merge request discussions via glab?▼

Managing GitLab merge request discussions via glab requires GitLab API access, URL-encoded project paths, and proper handling of discussion and note IDs to interact with paginated discussion lists.

How do I handle paginated discussion lists when responding to GitLab merge request reviews?▼

Handling paginated discussion lists in GitLab merge request reviews requires iterating through the pages to locate the correct discussion ID before posting your nested response or deleting notes via glab.