Verified:GitHub

gitlab-api

Name: gitlab-api
Availability: InStock
Author: pantheon-org

Fetch and analyze GitLab merge request comments and metadata via authenticated API calls.

9|Updated Feb 21, 2026

Search Tags:#automation #code review #feedback #api #comments #gitlab #merge request

Ready to run

npx skills add https://github.com/pantheon-org/tekhne --skill gitlab-api-pantheon-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gitlab-api
Source: https://github.com/pantheon-org/tekhne/tree/main/skills/specialized/gitlab-api
Command: npx skills add https://github.com/pantheon-org/tekhne --skill gitlab-api-pantheon-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the retrieval and analysis of GitLab merge request (MR) comments and metadata, streamlining code review processes and providing insights into discussion trends.

Core Features & Use Cases

Fetch MR Comments: Retrieve all comments, including diff notes and general discussions, from a specified GitLab MR.
Analyze Review Feedback: Filter and process comments to understand reviewer feedback, identify action items, and track review progress.
Use Case: When a merge request has many comments, use this Skill to quickly generate a summary report of all feedback, distinguishing between code-level comments and general discussion, and highlighting comments from human reviewers.

Quick Start

Use the gitlab-api skill to fetch all comments for the merge request at https://gitlab.com/your-group/your-project/-/merge_requests/123.

Frequently Asked Questions about gitlab-api

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

FAQPage Schema

How do I fetch and analyze GitLab merge request comments via API?▼

GitLab merge request comments are retrieved by making authenticated API calls to fetch discussion threads, diff notes, and reviewer feedback. The tool processes these responses to analyze review feedback and track MR progress.

Can I filter unresolved discussions from GitLab MR code reviews?▼

Unresolved discussions can be filtered from GitLab MR code reviews by processing comment metadata to isolate open threads. This distinguishes actionable reviewer feedback and tracks outstanding items within the merge request.

What dependencies do I need to retrieve GitLab MR metadata using curl and jq?▼

Retrieving GitLab MR metadata requires curl and jq installed locally, alongside a configured GITLAB_TOKEN with read_api scope. These dependencies execute authenticated HTTP requests and parse JSON responses to extract merge request data.

Does this approach separate general discussions from code-level diff notes?▼

The approach separates general discussions from code-level diff notes by analyzing fetched MR comment metadata. This distinction generates summary reports that differentiate project-level conversations from specific code review feedback.

What is the best way to consolidate GitLab reviewer feedback for MR progress tracking?▼

Consolidating GitLab reviewer feedback involves fetching all MR comments via authenticated API calls, then filtering threads to highlight human reviewer input. This generates an MR activity report tracking code review progress and discussion trends.

Why do I need a GITLAB_TOKEN with read_api scope for MR comment analysis?▼

A GITLAB_TOKEN with read_api scope is required for MR comment analysis to authenticate API requests against the GitLab instance. Without this token, API calls cannot authorize access to retrieve merge request metadata or comment threads.