mcpField
G
gitlab

gitlab

github.com/openhandsDevelopment17990 installsUpdated 2d ago
Repository

About gitlab

A GitLab skill that guides agents through GitLab operations. It prioritizes available authenticated GitLab MCP tools, otherwise uses the GitLab API with `GITLAB_TOKEN`, and provides rules for branch and merge request workflows.

Key features

  1. 01Prefer authenticated GitLab MCP tools
  2. 02Use GitLab API with `GITLAB_TOKEN`
  3. 03Open merge requests with `create_mr`
  4. 04Follow branch and push safeguards
  5. 05Handle token-based remote configuration

Use cases

  1. 01Choose between MCP tools and API access
  2. 02Create a merge request for requested changes
  3. 03Push work on a separate branch
  4. 04Resolve token-related push authentication issues

MCP support

The skill directs agents to use authenticated GitLab MCP tools when available. Otherwise, it provides GitLab API instructions using `GITLAB_TOKEN`.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/openhands/extensions --skill gitlab

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

Bundled files.plugin/plugin.jsonREADME.md

Details

From the project README

Connection selection

Use authenticated GitLab MCP tools first when they are available in the agent's environment. Detect this by tool availability, without depending on a particular MCP server name. Use the token and direct API instructions below only when GitLab MCP tools are unavailable or when raw API or curl access is explicitly needed.

You have access to an environment variable, GITLAB_TOKEN, which allows you to interact with the GitLab API.

You can use `curl` with the `GITLAB_TOKEN` to interact with GitLab's API. ALWAYS use the GitLab API for operations instead of a web browser. ALWAYS use the `create_mr` tool to open a merge request

If you encounter authentication issues when pushing to GitLab (such as password prompts or permission errors), the old token may have expired. In such case, update the remote URL to include the current token: git remote set-url origin https://oauth2:${GITLAB_TOKEN}@gitlab.com/username/repo.git

Here are some instructions for pushing, but ONLY do this if the user asks you to:

  • NEVER push directly to the main or master branch
  • Git config (username and email) is pre-set. Do not modify.
  • You may already be on a branch starting with openhands-workspace. Create a new branch with a better name before pushing.
  • Use the create_mr tool to create a merge request, if you haven't already
  • Once you've created your own branch or a merge request, continue to update it. Do NOT create a new one unless you are explicitly asked to. Update the PR title and description as necessary, but don't change the branch name.
  • Use the main branch as the base branch, unless the user requests otherwise
  • After opening or updating a merge request, send the user a short message with a link to the merge request.
  • Do all of the above in as few steps as possible. E.g. you could push changes with one step by running the following bash commands:
git remote -v && git branch # to find the current org, repo and branch
git checkout -b create-widget && git add . && git commit -m "Create widget" && git push -u origin create-widget

On Windows PowerShell, use $env:GITLAB_TOKEN in remote URLs and run the git commands as separate commands if && is not supported by the installed shell.

Comments

Markdown supported