gitlab-mr-issue
Manage GitLab MRs and Issues
GitLab issue and merge request work often needs exact CLI commands and consistent descriptions. This skill guides Claude, Codex, and Claude Code through glab workflows for viewing, creating, and updating GitLab items.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "gitlab-mr-issue" from https://skillstore.io/skills/dcjanus-gitlab-mr-issue.md and its manifest at https://skillstore.io/api/skills/dcjanus-gitlab-mr-issue/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "gitlab-mr-issue". Review merge request 45 and tell me what changed.
Expected outcome:
The response summarizes the merge request title, status, author, linked issues, and main diff areas. It highlights review risks and names any missing testing notes.
Using "gitlab-mr-issue". Create an issue for the failing payment retry job.
Expected outcome:
The response drafts a clear issue title, a short context and expected-result description, suggested labels, and the final GitLab issue URL after creation.
Using "gitlab-mr-issue". Update the MR description after I added integration tests.
Expected outcome:
The response reads the existing description, adds the testing update in the right section, and confirms the changed merge request URL.
Security Audit
SafeStatic analysis flagged Markdown command examples and a high-entropy heuristic, but the reviewed file is plain GitLab CLI documentation. No prompt injection, obfuscated payload, filesystem traversal, or hidden execution path was found in SKILL.md.
Risk Factors
⚙️ External commands (36)
📁 Filesystem access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/dcjanus-gitlab-mr-issue/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/dcjanus-gitlab-mr-issue?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/dcjanus-gitlab-mr-issue?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dcjanus-gitlab-mr-issue/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/dcjanus-gitlab-mr-issue.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
DCjanus. (2026). gitlab-mr-issue security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dcjanus-gitlab-mr-issue/audits/8BibTeX citation
@techreport{dcjanus-dcjanus-gitlab-mr-issue-2026,
author = {DCjanus},
title = {gitlab-mr-issue security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/dcjanus-gitlab-mr-issue/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "gitlab-mr-issue security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "DCjanus"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/dcjanus-gitlab-mr-issue/audits/8"
identifiers:
- type: other
value: "skillstore:dcjanus-gitlab-mr-issue:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prepare a Merge Request
Draft a non-interactive GitLab merge request with a clear title, formatted description, labels, and source branch.
Review MR Context
Inspect merge request details, linked issues, comments, and diffs before review or follow-up changes.
Triage GitLab Issues
List, view, comment on, and update issues across a GitLab project with consistent CLI commands.
Try These Prompts
Use this skill to view GitLab issue 123 with comments. Summarize the current status and any requested follow-up.
Use this skill to inspect merge request 45. Include the title, state, author, related issues, and the main diff themes.
Use this skill to create a GitLab merge request from the current branch to main. Draft a semantic title and a concise description with summary, key changes, constraints, and testing.
Use this skill to update merge request 45. Read the current title and description first, then propose the exact title and description changes before applying them.
Best Practices
- Confirm the GitLab host, project, and current user before creating or updating remote items.
- Read the current issue or merge request content before changing titles, descriptions, or labels.
- Keep merge request descriptions focused on what changed, why it matters, impact, constraints, and testing.
Avoid
- Do not run create or update commands without confirming the target project and branch.
- Do not replace an existing description before reading its current content.
- Do not use vague merge request titles that omit the feature, fix, or affected area.