mcpField
C
cyrus-setup-gitlab

cyrus-setup-gitlab

github.com/cyrusagentsDevelopment879791 installsUpdated today
Repository

About cyrus-setup-gitlab

A Cyrus skill that configures GitLab authentication through glab and sets Git’s global commit identity. It supports interactive sign-in, including self-hosted GitLab hostnames.

Key features

  1. 01Check existing glab authentication
  2. 02Sign in with glab
  3. 03Set Git’s global name and email
  4. 04Verify authentication and identity settings

Use cases

  1. 01Prepare Cyrus to create GitLab branches and merge requests
  2. 02Configure GitLab access for a self-hosted instance

Install

Copy the command and run it in a terminal.

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

After installing, type/cyrus-setup-gitlabin Claude Code to confirm it loaded.

Details

From the project README

CRITICAL: Never use Read, Edit, or Write tools on ~/.cyrus/.env or any file inside ~/.cyrus/. Use only Bash commands (grep, printf >>, etc.) to interact with env files — secrets must never be read into the conversation context.

Setup GitLab

Configures GitLab CLI and git so Cyrus can create branches, commits, and merge requests.

Step 1: Check Existing Configuration

Check if glab is already authenticated:

glab auth status 2>&1

If authenticated, check git config:

git config --global user.name
git config --global user.email

If both glab auth and git config are set, inform the user:

GitLab is already configured. Skipping this step.

Skip to completion.

Step 2: Authenticate GitLab CLI

If glab is not authenticated:

glab auth login

This opens an interactive browser flow. Let the user complete it.

For self-hosted GitLab instances, the user can specify the hostname:

glab auth login --hostname gitlab.example.com

After completion, verify:

glab auth status

Step 3: Configure Git Identity

If git user name or email are not set, ask the user for their preferred values:

What name should appear on commits made by Cyrus? (e.g., your name, or "Cyrus Bot")

What email should appear on commits? (e.g., your email, or a noreply address)

Then set them:

git config --global user.name "<name>"
git config --global user.email "<email>"

Step 4: Verify

glab auth status
git config --global user.name
git config --global user.email

Completion

✓ GitLab CLI authenticated ✓ Git identity configured: <name> <email>

Comments

Markdown supported