Verified:GitHub

gitlab

Retrieve GitLab CI/CD pipeline status, merge requests, and create issues via REST API.

Updated Aug 23, 2026

Search Tags:#devops #ci/cd #issues #gitlab #pipelines #merge requests

One-click install

npx skills add https://github.com/knsiuss/orion --skill gitlab-knsiuss

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: gitlab
Source: https://github.com/knsiuss/orion/tree/main/workspace/skills/gitlab
Command: npx skills add https://github.com/knsiuss/orion --skill gitlab-knsiuss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the management of GitLab projects by providing quick access to CI/CD status, merge requests, and issue tracking, reducing the need to navigate the GitLab web interface for common tasks.

Core Features & Use Cases

CI/CD Monitoring: Check the status of pipelines on specific branches.
Merge Request Management: View and interact with open merge requests.
Issue Tracking: Create and manage issues within projects.
Use Case: Quickly check if the latest pipeline for the main branch has passed before merging a feature.

Quick Start

Check the status of the latest pipeline on the main branch.

Frequently Asked Questions about gitlab

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

FAQPage Schema

How do I check my GitLab CI/CD pipeline status without opening the browser?▼

To check GitLab CI/CD pipeline status, this Skill retrieves the latest branch state via the GitLab REST API. It requires configuring GITLAB_TOKEN and GITLAB_URL environment variables for authentication to fetch current pipeline results directly.

How can I list open merge requests for a GitLab project using an API token?▼

Listing open merge requests is done by identifying your GitLab project by name or namespace. Once you provide your GITLAB_TOKEN and GITLAB_URL, the Skill securely queries the GitLab REST API to return all active merge requests.

What do I need to configure before creating GitLab issues programmatically?▼

Before creating GitLab issues, you must set the GITLAB_TOKEN and GITLAB_URL environment variables for endpoint access and authentication. The Skill then uses these credentials to interact with the GitLab REST API and generate issues in your specified project.

Does this GitLab project management approach work with self-hosted instances?▼

Yes, GitLab project management via this Skill supports self-hosted instances by utilizing the GITLAB_URL environment variable. You simply configure the URL to point to your custom endpoint, allowing CI/CD monitoring and issue tracking on your server.

Can I identify a GitLab project by name instead of a numeric ID?▼

Yes, you can identify a GitLab project by its name or namespace. This avoids needing numeric IDs for GitLab project management, streamlining how you retrieve CI/CD pipeline status, view merge requests, and create issues.

Why do my GitLab API requests fail when trying to view pipelines?▼

GitLab API requests to view pipelines fail if the GITLAB_TOKEN and GITLAB_URL environment variables are not properly configured. Accurate endpoint access and authentication credentials are strictly required to retrieve CI/CD pipeline status successfully.