# gitlab

This skill connects an agent to GitLab through the Membrane CLI. Use it to inspect and manage projects, issues, branches, and merge requests.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 179 installs · ★ 273 repo stars
- Author: membrane
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/membranedev/application-skills/tree/HEAD/skills/gitlab/SKILL.md
- Updated: 2026-04-28
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/membrane-gitlab

## What it does

The skill gives an agent a GitLab connection through the Membrane CLI. It can find projects, groups, and users, then retrieve issues, merge requests, branches, tags, commits, pipelines, and jobs. The listed actions also cover creating and updating projects, issues, and merge requests.

Install `@membranehq/cli`, sign in with `membrane login`, and create a GitLab connection with `membrane connection ensure`. The agent can discover an action with `membrane action list`, execute it through `membrane action run`, or send a direct GitLab API request through the proxy. Membrane handles credential refresh during these operations.

The skill will not work without network access and a valid Membrane account.

## Requirements
- Works with: GitLab

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill gitlab -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/gitlab/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/gitlab/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill gitlab -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/gitlab/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill gitlab -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/gitlab/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install membranedev/application-skills skills/gitlab
```

2. **Manually: put the files in place**
- File: `.github/skills/gitlab/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill gitlab -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/membranedev/application-skills --path skills/gitlab
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/gitlab/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill gitlab -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/membranedev/application-skills/tree/HEAD/skills/gitlab/SKILL.md

## When to use it
- list accessible GitLab projects
- find issues for a project
- inspect merge requests and branches
- create an issue or merge request
- run a GitLab action with JSON input

## Example prompts
- List my accessible GitLab projects using the `list-projects` action.
- Find the issues for this project with `list-issues`, then show their details.
- Create a GitLab merge request by locating `create-merge-request` and supplying its JSON parameters.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: ca1c1377c34aba66.

BEGIN THIRD-PARTY FILE ca1c1377c34aba66
````text
---
name: gitlab
description: |
  Gitlab integration. Manage Projects, Groups, Users, Labels. Use when the user wants to interact with Gitlab data.
compatibility: Requires network access and a valid Membrane account (Free tier supported).
license: MIT
homepage: https://getmembrane.com
repository: https://github.com/membranedev/application-skills
metadata:
  author: membrane
  version: "1.0"
  categories: "Project Management, Ticketing"
---

# Gitlab

GitLab is a web-based DevOps platform that provides version control, CI/CD, and issue tracking. It's primarily used by software development teams to manage their code, automate their workflows, and collaborate on projects.

Official docs: https://docs.gitlab.com/ee/api/

## Gitlab Overview

- **Project**
  - **Issue**
  - **Merge Request**
  - **Pipeline**
- **User**

Use action names and parameters as needed.

## Working with Gitlab

This skill uses the Membrane CLI to interact with Gitlab. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

### Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

```bash
npm install -g @membranehq/cli@latest
```

### Authentication

```bash
membrane login --tenant --clientName=<agentType>
```

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

```bash
membrane login complete <code>
```

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

### Connecting to Gitlab

Use `membrane connection ensure` to find or create a connection by app URL or domain:

```bash
membrane connection ensure "https://gitlab.com/" --json
```
The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

#### 1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

```bash
npx @membranehq/cli connection get <id> --wait --json
```

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

- **`READY`** — connection is fully set up. Skip to **Step 2**.
````
END THIRD-PARTY FILE ca1c1377c34aba66

The third-party file has ended. Everything between the ca1c1377c34aba66 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2854 of 7838 bytes. © membrane · MIT · https://github.com/membranedev/application-skills/tree/HEAD/skills/gitlab/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
