gitlab
Skill7 starsChanged 8 months agoMITView on GitHub
GitLab 操作。用于:(1) 管理 GitLab 项目和仓库 (2) 操作 Merge Request (3) 触发 CI/CD Pipeline (4) 管理文件和代码 (5) 管理用户和权限
- Reads credentials
- Installs packages
- Sends data out
Files
GitLab Skill
配置
# ~/.openclaw/workspace/.env
GITLAB_URL=https://gitlab.example.com
GITLAB_TOKEN=your-gitlab-private-token获取 Token
- 登录 GitLab → 点击头像 → Preferences
- 左侧菜单选择 "Access Tokens"
- 填写 Name,勾选
api或需要的权限 - 点击 "Create personal access token"
- 复制生成的 token
操作示例
source ~/.openclaw/workspace/.env项目操作
source ~/.openclaw/workspace/.env
# 列出用户项目
curl -s -H "PRIVATE-TOKEN: $GITLAB_TOKEN" \
"$GITLAB_URL/api/v4/projects?membership=true&owned=true" | jq '.[].name'
# 获取项目详情
curl -s -H "PRIVATE-TOKEN: $GITLAB_TOKEN" \
"$GITLAB_URL/api/v4/projects/ PROJECT_ID"
# 获取项目文件
curl -s -H "PRIVATE-TOKEN: $GITLAB_TOKEN" \
"$GITLAB_URL/api/v4/projects/ PROJECT_ID/repository/files/PATH?ref=BRANCH"Merge Request 操作
source ~/.openclaw/workspace/.env
# 列出 MR
curl -s -H "PRIVATE-TOKEN: $GITLAB_TOKEN" \
"$GITLAB_URL/api/v4/projects/ PROJECT_ID/merge_requests?state=opened"
# 创建 MR
curl -s -X POST -H "PRIVATE-TOKEN: $GITLAB_TOKEN" \
--data-urlencode "source_branch=feature-xxx" \
--data-urlencode "target_branch=main" \
--data-urlencode "title=Feature XXX" \
"$GITLAB_URL/api/v4/projects/ PROJECT_ID/merge_requests"
# 接受 MR
curl -s -X PUT -H "PRIVATE-TOKEN: $GITLAB_TOKEN" \
"$GITLAB_URL/api/v4/projects/ PROJECT_ID/merge_requests/ IID/merge"Pipeline 操作
source ~/.openclaw/workspace/.env
# 触发 Pipeline
curl -s -X POST -H "PRIVATE-TOKEN: $GITLAB_TOKEN" \
--data-urlencode "ref=main" \
"$GITLAB_URL/api/v4/projects/ PROJECT_ID/pipeline"
# Pipeline 状态
curl -s -H "PRIVATE-TOKEN: $GITLAB_TOKEN" \
"$GITLAB_URL/api/v4/projects/ PROJECT_ID/pipelines"
# 获取 Pipeline 日志
curl -s -H "PRIVATE-TOKEN: $GITLAB_TOKEN" \
"$GITLAB_URL/api/v4/projects/ PROJECT_ID/pipelines/ PIPELINE_ID/jobs"使用 glab CLI
# 安装: brew install glab
# 配置: glab auth login
glab repo list
glab mr list
glab mr create --source-branch feature --target-branch main --title "Feature"
glab pipeline run常用场景
- 创建 MR: 代码合并请求
- 触发构建: 启动 CI/CD Pipeline
- 查看状态: 检查 MR/Pipeline 状态
- 管理文件: 读取/修改仓库文件
使用场景
场景 1: 自动创建 Merge Request
当分支开发完成后自动创建 MR:
source ~/.openclaw/workspace/.env
# 创建 MR
MR_IID=$(curl -s -X POST -H "PRIVATE-TOKEN: $GITLAB_TOKEN" \
--data-urlencode "source_branch=feature-user-auth" \
--data-urlencode "target_branch=main" \
--data-urlencode "title=Feature: 用户认证模块" \
--data-urlencode "description=实现用户登录注册功能\n\nCloses #123" \
"$GITLAB_URL/api/v4/projects/$PROJECT_ID/merge_requests" | \
jq -r '.iid')
echo "MR created: !$MR_IID"场景 2: 触发 Pipeline 并等待完成
触发部署流水线并等待结果:
source ~/.openclaw/workspace/.env
# 触发 Pipeline
PIPELINE_ID=$(curl -s -X POST -H "PRIVATE-TOKEN: $GITLAB_TOKEN" \
--data-urlencode "ref=main" \
--data-urlencode "variables[0][key]=DEPLOY_ENV&variables[0][value]=production" \
"$GITLAB_URL/api/v4/projects/$PROJECT_ID/pipeline" | \
jq -r '.id')
# 等待完成
while true; do
STATUS=$(curl -s -H "PRIVATE-TOKEN: $GITLAB_TOKEN" \
"$GITLAB_URL/api/v4/projects/$PROJECT_ID/pipelines/$PIPELINE_ID" | \
jq -r '.status')
[[ "$STATUS" == "success" || "$STATUS" == "failed" ]] && break
sleep 15
done
echo "Pipeline $STATUS"场景 3: 批量更新文件
批量修改多个仓库的配置:
source ~/.openclaw/workspace/.env
# 更新 .gitlab-ci.yml
curl -X PUT -H "PRIVATE-TOKEN: $GITLAB_TOKEN" \
-H "Content-Type: application/json" \
--data '{"branch": "main", "author_email": "ci@gitlab.com", "content": "'$(base64 -w0 .gitlab-ci.yml)'", "commit_message": "Update CI config"}' \
"$GITLAB_URL/api/v4/projects/$PROJECT_ID/repository/files/.gitlab-ci.yml"Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- microsoft/hve-core★ 1.6ksame name
- refly-ai/refly-skills★ 203same name
- OpenHands/extensions★ 167same name
- AceDataCloud/Skills★ 17same name
- G1Joshi/Agent-Skills★ 15same name
- odyssey4me/agent-skills★ 13same name
- SHYXIN/skills★ 5same name
- apideck-libraries/api-skills★ 4same name
- fworks-tech/agenthood★ 3same name
- caosiwei97/agent-skills★ 2same name
4 more not listed
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.
Used alongsideProjects with it also use linear.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OpenAISkilllinear
Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.
Also in 3 projects that use this
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.

