GitLab Issue

Create, retrieve, update, list GitLab issues on self-hosted GitLab instances.

Updated Aug 23, 2026

Search Tags:#automation #templates #issues #workflows #GitLab #self-hosted #manage

One-click install

npx skills add https://github.com/Dedalus-ERP-PAS/foundation-skills --skill gitlab-issue

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: GitLab Issue
Source: https://github.com/Dedalus-ERP-PAS/foundation-skills/tree/main/skills/gitlab-issue
Command: npx skills add https://github.com/Dedalus-ERP-PAS/foundation-skills --skill gitlab-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing GitLab issues across projects and teams often involves manual, repetitive steps, inconsistent descriptions, and scattered context. This Skill provides a structured way to create, retrieve, update, list, and link issues with consistent templates and context.

Core Features & Use Cases

Create, retrieve, update, and list issues across a self-hosted GitLab instance.
Enforce best practices: validate project_id before operations, prevent duplicate issues, and guide users with templates.
Link issues to related merge requests, milestones, and labels to streamline project workflows.
Use in scenarios such as triaging bugs, planning features, and tracking tasks within a project.

Quick Start

Example: Create a new issue in namespace/project with a descriptive title and a detailed description to track a new work item.

Frequently Asked Questions about GitLab Issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate GitLab issue creation with consistent templates and context?▼

Automating GitLab issue creation involves using structured workflows that validate project IDs, prevent duplicate issues, and guide users through issue templates to ensure consistent descriptions across self-hosted instances.

Does this GitLab issue workflow support self-hosted instances?▼

Yes, this workflow supports self-hosted GitLab instances, allowing teams to create, retrieve, update, list, and link issues directly within their self-hosted environment.

What's the best way to manage and link GitLab issues to milestones and merge requests?▼

The best way to manage and link GitLab issues is through structured workflows that connect issues to related merge requests, milestones, and labels, streamlining project workflows and ensuring all context is properly associated.

How do I prevent duplicate issues when managing multiple GitLab projects?▼

Preventing duplicate issues requires using workflows that enforce best practices by validating project IDs before operations and prompting for context, ensuring redundant issues are caught before creation across projects.

Can I list and retrieve issues across different projects in a self-hosted GitLab instance?▼

Yes, you can list and retrieve issues across different projects in a self-hosted GitLab instance by using structured management workflows that validate project IDs and enforce consistent context retrieval for each operation.

Why validate project IDs before creating or updating GitLab issues?▼

Validating project IDs before creating or updating GitLab issues enforces best practices by ensuring operations target the correct repository, preventing duplicate issues, and maintaining accurate context and linking across workflows.