cyrus-setup-gitlab
Skill888 starsChanged 53 days agoApache-2.0View on GitHub
Configure GitLab authentication for Cyrus — glab CLI login and git config for creating merge requests.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- cyrusagents/cyrusword for word, first seen Sep 24, 2026
Other versions1 project uses a version of this.
Word for word · 1
- cyrusagents/cyrus★ 902100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- packages/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- googleSkill
- release-core-testSkill
- cyrus-setup-claude-authSkill
- cyrus-setup-endpointSkill
- cyrus-setup-githubSkill
- cyrus-setup-launchSkill
- cyrus-setup-linearSkill
- cyrus-setup-prerequisitesSkill
- cyrus-setup-repositorySkill
- cyrus-setupSkill
- cyrus-setup-slackSkill
- debugSkill
- f1-test-driveSkill
- implementationSkill
- investigateSkill
- releaseSkill
- summarizeSkill
- verify-and-shipSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Check if glab is already authenticated:
- Distinctive: line 20
If authenticated, check git config:
- Very specific: line 27
If both glab auth and git config are set, inform the user:
- Very specific: line 35
If glab is not authenticated:
- Distinctive: line 57
If git user name or email are not set, ask the user for their preferred values:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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>&1If authenticated, check git config:
git config --global user.name
git config --global user.emailIf 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 loginThis 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.comAfter completion, verify:
glab auth statusStep 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.emailCompletion
✓ GitLab CLI authenticated ✓ Git identity configured:
<name><
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

