Verified:GitHub

cyrus-setup-gitlab

Configures GitLab CLI authentication and git identity for Cyrus merge request workflows.

794|163|Updated Apr 19, 2025

Search Tags:#merge requests #Authentication #GitLab #Setup #cyrus #glab CLI #git config

One-click install

npx skills add https://github.com/ceedaragents/cyrus --skill cyrus-setup-gitlab

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: cyrus-setup-gitlab
Source: https://github.com/ceedaragents/cyrus/tree/main/skills/cyrus-setup-gitlab
Command: npx skills add https://github.com/ceedaragents/cyrus --skill cyrus-setup-gitlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up GitLab access for an automated agent requires correctly authenticating the glab CLI and configuring git identity, and misconfiguration causes branch, commit, and merge request operations to fail.

Core Features & Use Cases

Existing Configuration Detection: Checks glab auth status and git config first, skipping setup when GitLab is already configured.
GitLab CLI Authentication: Guides the user through glab auth login, including support for self-hosted GitLab instances via custom hostnames.
Git Identity Setup: Prompts for and sets the global git user name and email used on commits made by Cyrus.
Use Case: While onboarding Cyrus for a GitLab-based repository, run this skill so the agent can authenticate glab, configure commit identity, and verify everything before creating merge requests.

Quick Start

Ask the agent to set up GitLab authentication and git identity for Cyrus so it can create branches and merge requests.

Frequently Asked Questions about cyrus-setup-gitlab

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

FAQPage Schema

How do I authenticate the GitLab CLI for an automated agent?▼

Run glab auth login to start an interactive browser-based authentication flow, then verify with glab auth status. For self-hosted GitLab, pass the hostname with glab auth login --hostname gitlab.example.com.

How do I configure git user name and email for commits?▼

Set the identity globally with git config --global user.name and git config --global user.email. The skill prompts for preferred values, such as a personal name or a bot identity like Cyrus Bot with a noreply email.

Does this GitLab setup work with self-hosted GitLab instances?▼

Yes, self-hosted GitLab is supported by specifying the instance hostname during login, for example glab auth login --hostname gitlab.example.com. Verification uses the same glab auth status command afterward.

What happens if GitLab is already configured before running setup?▼

The skill first checks glab auth status and the existing git user name and email. If both are already set, it reports that GitLab is configured and skips directly to completion without changes.

Why should the agent avoid reading the ~/.cyrus/.env file?▼

The env file contains secrets that must never enter the conversation context. The skill restricts interaction to Bash commands like grep and printf append operations instead of Read, Edit, or Write tools.