gitlab-ops

Standardize GitLab and GitHub CLI usage with dynamic project resolution.

50|7|Updated Apr 2, 2026

Search Tags:#github #gitlab #vcs #gh #issue-management #glab #label-taxonomy

One-click install

npx skills add https://github.com/Kanevry/session-orchestrator --skill gitlab-ops

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: gitlab-ops
Source: https://github.com/Kanevry/session-orchestrator/tree/main/skills/gitlab-ops
Command: npx skills add https://github.com/Kanevry/session-orchestrator --skill gitlab-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and standardizes VCS operations across GitLab and GitHub so consuming skills and human operators avoid duplicated detection logic, inconsistent CLI usage, and hardcoded project identifiers.

Core Features & Use Cases

VCS Auto-Detection: Guidance to detect whether a repository uses GitLab or GitHub and which CLI to invoke.
Canonical CLI Commands: Curated, canonical glab and gh command examples for listing, viewing, creating, and updating issues/merge requests and pipelines.
Dynamic Project Resolution & Taxonomy: Patterns and API techniques to resolve project IDs or owner/name slugs dynamically, plus a recommended label taxonomy and issue templates for consistent triage.
Use Case: Integrate into an agent-driven session to automatically detect the platform, list ready issues, create an issue with the correct labels, and resolve cross-project references without hardcoding IDs.

Quick Start

Use the gitlab-ops reference to detect the repository VCS and follow the recommended CLI and resolution steps to list and manage issues and merge requests.

Frequently Asked Questions about gitlab-ops

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

FAQPage Schema

How do I standardize GitLab and GitHub CLI usage across different projects?▼

Standardize GitLab and GitHub CLI usage by applying canonical glab and gh command syntax for repository operations, ensuring consistent issue and merge request management across both platforms without duplicated detection logic.

How do I dynamically resolve project identifiers for GitLab and GitHub APIs?▼

Dynamically resolve project identifiers by using API techniques and patterns to fetch project IDs or owner/name slugs at runtime, eliminating the need to hardcode project identifiers in your automation workflows.

Can I automatically detect whether a repository uses GitLab or GitHub?▼

Yes, you can automatically detect the repository VCS platform. The system provides guidance to determine whether a repository uses GitLab or GitHub and identifies which CLI tool to invoke for subsequent operations.

What is the best way to enforce consistent label taxonomy for issue management across VCS platforms?▼

Enforce consistent label taxonomy by applying a recommended label taxonomy and standardized issue templates during issue creation, ensuring consistent triage and categorization across GitLab and GitHub repositories.

How do I manage cross-project queries during agent-driven workflows on GitHub and GitLab?▼

Manage cross-project queries by leveraging dynamic project resolution and canonical CLI commands within agent-driven sessions, allowing seamless listing, creation, and updating of issues and merge requests across multiple repositories.