Gitlab Skill

GitLab integration for fetching issues/MRs, generating executive summaries, performing comprehensive code reviews, and automating issue resolution workflows. Use when working with GitLab issues, merge requests, or when asked to summarize, review, comment on, or resolve GitLab work items.

5 stars 1 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add ekohe/gitlab-skill --skill gitlab-skill
Manual install
git clone --depth 1 https://github.com/ekohe/gitlab-skill.git /tmp/gitlab-skill
mkdir -p ~/.claude/skills
cp -r /tmp/gitlab-skill/. ~/.claude/skills/gitlab-skill

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# GitLab Integration

## Purpose

This skill provides comprehensive GitLab integration capabilities, enabling automated workflows for issue management, code review, and project insights. It bridges GitLab data with intelligent analysis and action, supporting both read operations (summaries, reviews) and write operations (posting comments, creating merge requests).

## When to Use This Skill

Invoke this skill when:
- Fetching or analyzing GitLab issues or merge requests
- Generating executive summaries of issues
- Performing code reviews on merge requests
- Posting comments or updates to GitLab issues/MRs
- Automating issue resolution (fetch issue → implement fix → create MR)
- Aggregating project insights across multiple issues or MRs
- The user mentions GitLab issue numbers (e.g., "#123") or MR numbers (e.g., "!456")

## Prerequisites

### Configuration Setup

This skill supports multiple GitLab instances through a configuration file, making it easy to work with different GitLab servers (work, personal, clients, etc.).

**Option 1: Configuration File (Recommended for Multiple Instances)**

Create a `gitlab_config.json` file in one of these locations:
- `./gitlab_config.json` (current directory)
- `~/.gitlab/config.json` (user home directory)
- Next to the skill's scripts directory

Example configuration:
Read the full skill on GitHub

Details

Skill name
gitlab-skill
Repository
ekohe/gitlab-skill
License
MIT
Repo updated
11 February 2026

FAQ

What does the Gitlab Skill skill do?

GitLab integration for fetching issues/MRs, generating executive summaries, performing comprehensive code reviews, and automating issue resolution workflows. Use when working with GitLab issues, merge requests, or when asked to summarize, review, comment on, or resolve GitLab work items.

How do I install the Gitlab Skill skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add ekohe/gitlab-skill --skill gitlab-skill. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Gitlab Skill popular?

It lives in ekohe/gitlab-skill, which has 5 GitHub stars and 1 forks.

Related skills

Shipreel

3

theBstar/shipreel

Turn a pull request into a short narrated walkthrough video (about two and a half minutes) with animated diagrams, code panels, optional screen recordings of the real app, captions, crossfade cuts and an ambient music bed. Runs locally with no paid services by default. Use when asked for a PR video, PR walkthrough, demo video of a change, or "make a shipreel".

Git & Code ReviewIn 1 list

Auto Experiment

5

zxl696/smallmodel-auto-experiment-skill

自动化超参数/架构搜索循环。给定模型代码、数据集和优化目标，自动生成 train.py，经双 agent 审计门禁通过后，循环调用 DeepSeek 提出改进建议、训练、用 git 追踪每轮变更，保留最优配置和 checkpoint。

Git & Code Review

Dialog Tree

3

ikotelkin/claude-skills

Maintain a visual "dialog tree" — a data file plus a self-contained HTML viewer in the project repo that map the branches of a long conversation (user questions → the steps/variants of the answers) as an interactive tree with resolve/delete marks and a "built up to" marker for incremental updates. Use whenever the user asks to "create/set up a dialog tree", "update the tree", "add this to the tree", "show open branches", or mentions dialog-tree.html — and proactively offer it when a deep-dive discussion branches enough that the user risks losing track of unexplored side-threads.

Git & Code ReviewIn 1 list

Blitz

6

ADM-NKH/claude-blitz

A continuously-firing background work runner for Claude Code. Queue real tasks ("/blitz add"), track long-term goals ("/blitz goal add"), and enable per-project audit rotations ("/blitz audit enable"). Blitz fires on a configurable cadence with a per-project idle gate, decomposes goals into increments on a long-lived branch, and persists every fire's output to ~/blitz/runs/<timestamp>/. Includes commands to manage the backlog, goals, audits, schedules, and kill switches (off/on/skip).

Git & Code Review

Structured Gist

2

domattioli/structured-gist

Render explanatory or process-recap prose as a nested lecture-note outline instead of paragraphs — fixed role ladder concept (-) → attribute (▸, a named property) → enumerator (I./A./i./a.) → explanation (↪, one prose sentence, usually a leaf). No plain bullets. Render modes — block (fenced, literal glyphs; default on every surface) and responsive (opt-in real GFM nested list for GitHub bodies and chat replies; glyph-free, role carried by typography). One granularity level (standard); skim and deep are archived. Independent of caveman (structure vs wording). Opt-in report preset (`/structured-

Git & Code ReviewIn 1 list

Worktree Closeout

6

leonsong09/worktree-closeout

Use when the user asks for worktree closeout, branch closeout, parallel closeout, worktree janitor, 工作树收口, 分支收口, or 并行收口, especially when work spans multiple Codex sessions and you need a date-based scan of open worktrees, closeout status, suggested merge/prune order, and prompt-ready handoff instructions.

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.