omnicreate-gitlab

omnicreate-gitlab is a skill for Claude Code from nexiouscaliver/OmniForge. It costs 45 tokens per session (2,287 once invoked), scanned A, original, MIT.

A GitLab merge-request creator for proposing code changes for review. It builds the request details from your commits and can set common review metadata.

In plain words
What is it for?
Creating GitLab merge requests, including draft requests, labels, assignees, reviewers, and links to issues.
Why use it?
It avoids writing the title and description from scratch and reduces missed setup details when opening a merge request.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the omniforge plugin — 8 skills shipped together

Good fit Creating GitLab merge requests, including draft requests, labels, assignees, reviewers, and links to issues.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nexiouscaliver/omniforge/omnicreate-gitlab
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add nexiouscaliver/OmniForge --skill omnicreate-gitlab
Clone the repo
git clone --depth 1 https://github.com/nexiouscaliver/OmniForge

Made for: Claude Code.

Or install omniforge, the plugin that ships this one along with the rest of its 8 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for omnicreate-gitlab

README.md
[![agentmods](https://agentmods.dev/badge/skills/nexiouscaliver/omniforge/omnicreate-gitlab/github.svg)](https://agentmods.dev/skills/nexiouscaliver/omniforge/omnicreate-gitlab)
Your own site
<a href="https://agentmods.dev/skills/nexiouscaliver/omniforge/omnicreate-gitlab"><img src="https://agentmods.dev/badge/skills/nexiouscaliver/omniforge/omnicreate-gitlab/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for omnicreate-gitlab

Your own site · 80×15
<a href="https://agentmods.dev/skills/nexiouscaliver/omniforge/omnicreate-gitlab"><img src="https://agentmods.dev/badge/skills/nexiouscaliver/omniforge/omnicreate-gitlab.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,287 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.02287
Opus 5 $0.00023 $0.01144
Sonnet 5 $0.00009 $0.00457
Haiku 4.5 $0.00005 $0.00229

Measured 9d ago against content hash 3b3aebbef9eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

omnicreate-gitlab scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/omniforge/skills/omnicreate-gitlab/SKILL.md · 205 lines

How it starts

The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitLab Merge Request Creator

Context

  • Current git status: !git status --porcelain
  • Current branch: !git branch --show-current
  • Recent commits: !git log --oneline -5
  • GitLab remote: !git remote -v | grep gitlab | head -1
  • glab version: !glab version 2>/dev/null || echo "NOT_INSTALLED"
  • glab auth status: !glab auth status 2>&1 || echo "NOT_AUTHENTICATED"
  • Unpushed commits: !git log @{u}..HEAD --oneline 2>/dev/null || echo "NO_UPSTREAM"
  • Repo root: !git rev-parse --show-toplevel 2>/dev/null || echo "NOT_A_GIT_REPO"

Your Task

Create a GitLab merge request using the mcp__omniforge__create_gitlab_mr MCP tool.

Why MCP instead of raw bash? The MCP tool validates all inputs, uses safe subprocess execution (no shell interpretation), and provides structured error output — making it safe for use by all models without risk of shell injection.

Prerequisites

  1. Verify glab is installed. If not, inform the user:
    brew install glab  # macOS
    
  2. Verify the current directory is a git repository with a GitLab remote.
  3. Ensure there are commits to create an MR from (not on main/master without changes).

Pre-Flight Checklist

Before creating the MR, verify:

  • glab is installed and authenticated
  • Not on main/master branch
  • Has commits to merge (not empty)
  • No uncommitted changes (warn if present)
  • Branch has upstream or can be pushed

MCP Tool: mcp__omniforge__create_gitlab_mr

Use this tool for all MR creation. It wraps glab mr create safely.

Required parameter:

  • repo_root: absolute path to the git repository root (from git rev-parse --show-toplevel)

Optional parameters (pass only what the user specified):

Parameter Type Default Description
title string "" Custom MR title (overrides fill)
description string "" Custom MR description (overrides fill)
target_branch string "main" Target branch for the MR
source_branch string "" Source branch (default: current branch)
assignees string "" Comma-separated usernames to assign
reviewers string "" Comma-separated usernames to request review from
labels string "" Comma-separated label names
draft bool false Mark as draft MR
fill bool true Auto-populate title/description from commits
fill_commit_body bool true Include commit bodies in description
push bool true Push branch if not already pushed
related_issue string "" Issue number to link MR to
copy_issue_labels bool false Copy labels from related issue
remove_source_branch bool false Delete source branch after merge
squash_before_merge bool false Squash commits when merging
milestone string "" Milestone ID or title
web bool false Open in browser for final editing

Read the full file on GitHub · 205 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 205 lines · 45 tokens per session scan A 3b3aebbef9eb

Subscribe to this mod's changes

omnicreate-gitlab is a skill published in the GitHub repository nexiouscaliver/OmniForge (4 stars, last pushed 4d ago), licensed MIT. It adds 45 tokens to every session and 2,287 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

pr-review

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

oliver-kriska/claude-elixir-phoenix · 59 tokens

phx-pr-review

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

oliver-kriska/claude-elixir-phoenix · 61 tokens

github-pr-creation

Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…

fvadicamo/dev-agent-skills · 75 tokens

pr-sweep

Use when you want to sweep all open pull requests across all repos, triage their status, run code reviews on unreviewed PRs, merge what's ready, fix quick blockers, and produce a full status report. Trigger when the user says "check my PRs", "close out open PRs", "what's the status of my PRs", "sweep my PRs", "PR…

harnessprotocol/harness-kit · 0 tokens

open-pr

Use when wrapping up a development task and getting a PR ready — runs local tests, creates a PR (if one doesn't exist) with a structured description template, conducts a code review via the review skill, and checks CI status with quick fixes. Trigger when the user says they're done with a feature, want to open a PR…

harnessprotocol/harness-kit · 111 tokens

fec-doc-sync

A workflow for keeping front-end project documentation aligned with the code and configuration that actually exist. It checks sources such as package files, routes, API clients, schemas, tests, continuous-integration settings, deployment files, and environment examples.

bovinphang/frontend-craft · 98 tokens