# Automate GitLab Workflows with Rube MCP

GitLab operations require repeated navigation, filtering, and identifier lookup across projects. This skill guides Claude, Codex, and Claude Code through Rube MCP workflows for repositories, pipelines, issues, and users.

## Install

```bash
npx skillstore add sickn33/gitlab-automation
```

## Metadata

- Status: approved
- Slug: sickn33-gitlab-automation
- Skillstore revision: r2
- Version status: missing
- Tree hash: b5b5e47a1142c517966e4d56ab66b8d13b972688a988b909dfcd90e28cb2d302
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/gitlab-automation
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 50
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/sickn33-gitlab-automation
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-gitlab-automation/manifest

## Capabilities

- Connects Rube MCP to GitLab through the documented OAuth workflow.
- Searches current tool schemas and resolves project, issue, pipeline, and user identifiers.
- Lists, creates, searches, and updates GitLab issues with labels, states, milestones, and assignees.
- Filters merge requests and inspects repository branches, commits, and language data.
- Lists projects, creates projects, and creates branches from a branch or commit reference.
- Monitors pipelines and jobs, then searches users and project membership.

## Use Cases

- Triage Project Issues: Find open issues, apply precise filters, resolve assignee identifiers, and prepare controlled updates.
- Investigate Pipeline Failures: Filter failed pipelines by branch and date, inspect pipeline details, and summarize affected jobs.
- Review Repository Access: List projects, inspect direct and inherited members, and check user status across selected repositories.

## Prompt Templates

### List Open Issues

```
Connect to GitLab and find project [project]. List its open issues with labels, assignees, and update dates. Do not change anything.
```

### Review Merge Requests

```
Find project [project]. List all open merge requests targeting [branch]. Include draft status, author, reviewers, labels, and recent update time.
```

### Investigate Failed Pipelines

```
Inspect failed pipelines for project [project] on ref [branch] since [date]. List failed jobs and summarize the latest failure. Keep requests paginated.
```

### Audit Projects and Members

```
Enumerate accessible projects matching [filter]. For each project, paginate through members and open issues. Highlight blocked users, unassigned issues, and incomplete coverage.
```

## Limitations

- Requires the external Rube MCP service and an active GitLab OAuth connection.
- Available actions depend on current Composio tool schemas and connected account permissions.
- Some filters and administration fields require GitLab Premium, Ultimate, owner, or administrator access.
- It does not document merge, approval, deletion, pipeline trigger, or pipeline cancellation workflows.

## Best Practices

- Search Rube tool schemas before each workflow because parameters can change.
- Verify connection status, project identifiers, internal IDs, branches, and permissions before dependent calls.
- Preview remote mutations, request confirmation, paginate complete result sets, and use narrow filters.

## Anti Patterns

- Do not assume the first page contains every project, issue, merge request, pipeline, or member.
- Do not confuse project-scoped issue and pipeline identifiers with global identifiers.
- Do not replace labels, change assignees, or create remote resources without reviewing the intended effect.

## Security Audit

- Audited at: 2026-07-24T00:08:58.579\+00:00
- Summary: The 145 external-command detections are false positives caused by Markdown backticks, and both reconnaissance detections describe normal GitLab validation or filtering. The skill intentionally connects to Rube MCP, delegates GitLab OAuth access, and permits remote mutations without an explicit confirmation step.

## Stats

- Views: 106
- Downloads: 10
- Favorites: 0
- Popularity score: 0