Search the web for information. Use when you need to look something up, find current information, or research a topic.
/cyrus-setup-gitlab
Configure GitLab authentication for Cyrus — glab CLI login and git config for creating merge requests.
Claude Code
$ npx -y skills add cyrusagents/cyrus --skill cyrus-setup-gitlab --agent claude-code
Codex
$ npx skills add cyrusagents/cyrus --skill cyrus-setup-gitlab -a codex -y
Cursor
$ npx skills add cyrusagents/cyrus --skill cyrus-setup-gitlab -a cursor -y
Gemini CLI
$ npx skills add cyrusagents/cyrus --skill cyrus-setup-gitlab -a gemini-cli -y
GitHub Copilot
$ npx skills add cyrusagents/cyrus --skill cyrus-setup-gitlab -a github-copilot -y
OpenCode
$ npx skills add cyrusagents/cyrus --skill cyrus-setup-gitlab -a opencode -y
Windsurf
$ npx skills add cyrusagents/cyrus --skill cyrus-setup-gitlab -a windsurf -y
SKILL.md
cyrus-setup-gitlab.SKILL.mdname: cyrus-setup-gitlab
description: Configure GitLab authentication for Cyrus — glab CLI login and git config for creating merge requests.
**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`>
Read more
name: cyrus-setup-gitlab description: Configure GitLab authentication for Cyrus — glab CLI login and git config for creating merge requests.
**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`>
Your (Claude Code|Codex|Cursor|Gemini|Opencode) powered (Linear|GitHub|GitLab|Slack) agent.
Other skills on cyrus.
release-core-test
Invoke when dev-testing a Cyrus change that spans CYPACK (edgeworker + CLI) and CYHOST (Vercel-hosted GUI) and the hosted GUI…
cyrus-setup-claude-aut…
Configure Claude Code authentication for Cyrus — API key, OAuth token, or third-party provider.
cyrus-setup-endpoint
Configure the public webhook endpoint for Cyrus — ngrok, Cloudflare Tunnel, or custom URL.
cyrus-setup-github
Configure GitHub for Cyrus — gh CLI login and git config for PRs, with optional webhook setup to enable @mention responses in PR…
cyrus-setup-launch
Print a summary of the Cyrus setup and offer to start the agent.
More skills from other plugins.
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…
Questions about cyrus-setup-gitlab.
- Which coding agents can use cyrus-setup-gitlab?
- cyrus-setup-gitlab installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

