Verified:GitHub

gitlab-devops

Automate GitLab issues, merge requests, pipelines, and repository browsing.

Updated Feb 28, 2026

Search Tags:#devops #gitlab #ci-cd #pipelines #version-control #change-management #merge-requests

One-click install

npx skills add https://github.com/dgethings/netclaw --skill gitlab-devops

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitLab DevOps teams struggle with coordinating issues, merge requests, pipelines, and repository metadata across projects, leading to slower delivery and governance gaps.

Core Features & Use Cases

Manage issues, merge requests, labels, milestones, releases, and wiki pages across GitLab projects.
Monitor CI/CD pipelines and explore project structure, files, and history to troubleshoot deployments.
Enforce safe, operator-confirmed workflows for mutating actions to ensure governance and auditability.

Quick Start

To begin, connect to a GitLab project and perform operator-approved queries of issues, merge requests, and pipelines.

Frequently Asked Questions about gitlab-devops

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

FAQPage Schema

How do I automate GitLab merge requests and pipeline monitoring across projects?▼

This Skill automates GitLab DevOps operations like merge requests, pipeline monitoring, and repository browsing across projects. It requires the gitlab-mcp server and enforces operator confirmation for mutating actions to ensure safe, auditable workflows.

What is the best way to manage GitLab issues and milestones for network projects?▼

Managing GitLab issues and milestones for network projects is done through automated DevOps workflows. This Skill queries project status, manages labels and releases, and enforces operator-approved workflows for governance and auditability across your projects.

Do I need a GitLab personal access token to monitor CI/CD pipelines?▼

Yes, monitoring CI/CD pipelines requires the GITLAB_PERSONAL_ACCESS_TOKEN environment variable. You must configure this token and connect the gitlab-mcp server to enable pipeline queries, repository browsing, and change management operations.

Can I safely automate write operations for GitLab labels and wiki content?▼

You can safely automate write operations for GitLab labels and wiki content because this Skill enforces a safe, read/write workflow with operator confirmation for all mutating actions. This guarantees governance and auditability across your projects.

How does operator confirmation work for mutating GitLab repository actions?▼

Operator confirmation for mutating GitLab repository actions requires explicit approval before executing write operations. This safe workflow ensures that changes to issues, merge requests, and releases remain auditable and governed across all managed projects.

Why does my GitLab CI/CD automation require operator approval for changes?▼

GitLab CI/CD automation requires operator approval for changes to enforce secure, auditable DevOps workflows. This governance measure prevents unauthorized modifications to pipelines, merge requests, and repository metadata across your network projects.