gitlab-issues
Use this skill when the user mentions "gitlab issues", "list issues", "show issues", "my issues", "milestone", "sprint", "create issue", "update issue", "assign issue", or wants to manage GitLab issues.
What this skill does
# GitLab Issues Integration
Manage GitLab issues using bash scripts. Create issues, create sub-issues, list issues, read comments, post updates, assign people, and create merge requests from issues.
## How to Use
**Call bash scripts directly via the Bash tool.** No MCP server required.
**Scripts location:** `~/.claude/plugins/cache/awesome-agent-toolkit/gitlab-issues/1.2.1/core/scripts/`
**IMPORTANT:** Environment variables must be set. Check with:
```bash
echo $GITLAB_HOST_URL $GITLAB_TOKEN $GITLAB_PROJECT_ID
```
If empty, add them to `~/.claude/settings.json` under `env`:
```json
{
"env": {
"GITLAB_HOST_URL": "https://gitlab.com",
"GITLAB_TOKEN": "glpat-xxxxxxxxxxxx",
"GITLAB_PROJECT_ID": "12345678"
}
}
```
## Available Commands
Set `PLUGIN_DIR=~/.claude/plugins/cache/awesome-agent-toolkit/gitlab-issues/1.2.1`
### Create Issue
```bash
# Create a simple issue (title only)
bash $PLUGIN_DIR/core/scripts/create-issue.sh '{"title": "Fix login bug"}'
# Create issue with description and labels
bash $PLUGIN_DIR/core/scripts/create-issue.sh '{"title": "Add dark mode", "description": "Implement dark mode toggle in settings", "labels": "feature,ui"}'
# Create issue with full details
bash $PLUGIN_DIR/core/scripts/create-issue.sh '{"title": "API rate limiting", "description": "Add rate limiting to public endpoints", "labels": "backend,security", "assignee_ids": [12], "milestone_id": 8, "due_date": "2025-03-01", "weight": 3}'
# Create a confidential issue
bash $PLUGIN_DIR/core/scripts/create-issue.sh '{"title": "Security vulnerability", "description": "Details...", "confidential": true}'
```
Returns created issue details including IID, URL, assignees, and labels.
### Create Sub-Issue (Child Issue)
```bash
# Create a sub-issue linked to parent issue #45
bash $PLUGIN_DIR/core/scripts/create-sub-issue.sh 45 '{"title": "Implement login form validation"}'
# Create sub-issue with description and labels
bash $PLUGIN_DIR/core/scripts/create-sub-issue.sh 45 '{"title": "Add unit tests for auth", "description": "Cover edge cases", "labels": "testing"}'
# Create sub-issue with assignee
bash $PLUGIN_DIR/core/scripts/create-sub-issue.sh 45 '{"title": "Update API docs", "assignee_ids": [15], "labels": "docs"}'
```
Creates a new issue and links it as a child of the parent issue. On GitLab Premium 16.0+ uses native parent/child hierarchy; otherwise falls back to a "relates_to" link.
### List Issues
```bash
# List open issues (default)
bash $PLUGIN_DIR/core/scripts/list-issues.sh
# List closed issues
bash $PLUGIN_DIR/core/scripts/list-issues.sh closed
# List all issues
bash $PLUGIN_DIR/core/scripts/list-issues.sh all
# List issues from a specific milestone
bash $PLUGIN_DIR/core/scripts/list-issues.sh opened "Sprint 23"
```
### Get Issue Details
```bash
bash $PLUGIN_DIR/core/scripts/get-issue-details.sh 45
```
Returns full issue details including description, assignees, labels, milestone.
### Get Issue Comments
```bash
bash $PLUGIN_DIR/core/scripts/get-issue-comments.sh 45
```
### Post Comment on Issue
```bash
bash $PLUGIN_DIR/core/scripts/post-issue-comment.sh 45 "Your comment here"
```
### Update Issue
```bash
# Update description
bash $PLUGIN_DIR/core/scripts/update-issue.sh 45 --description "New description"
# Assign users (by user ID)
bash $PLUGIN_DIR/core/scripts/update-issue.sh 45 --assignee-ids "12,15"
# Set milestone (by milestone ID)
bash $PLUGIN_DIR/core/scripts/update-issue.sh 45 --milestone-id 8
# Add labels
bash $PLUGIN_DIR/core/scripts/update-issue.sh 45 --labels "bug,urgent"
# Close issue
bash $PLUGIN_DIR/core/scripts/update-issue.sh 45 --state-event close
```
### List Milestones
```bash
bash $PLUGIN_DIR/core/scripts/list-milestones.sh
```
Use this to find milestone IDs for filtering or assigning.
### List Project Members
```bash
bash $PLUGIN_DIR/core/scripts/list-project-members.sh
```
Use this to find user IDs for assigning issues.
### Create MR from Issue
```bash
bash $PLUGIN_DIR/core/scripts/create-mr-from-issue.sh 45 feature/my-branch
```
Creates a merge request linked to the issue. Merging will auto-close the issue.
## Workflows
### 1. List Issues from Milestone
When user asks "show issues in Sprint 23":
1. Run: `bash $PLUGIN_DIR/core/scripts/list-milestones.sh` to find milestone
2. Run: `bash $PLUGIN_DIR/core/scripts/list-issues.sh opened "Sprint 23"`
3. Present as table with IID, title, assignees, labels
### 2. Get Issue and Post Update
When user asks about a specific issue:
1. Run: `bash $PLUGIN_DIR/core/scripts/get-issue-details.sh <iid>`
2. Display description and metadata
3. If user wants to comment: `bash $PLUGIN_DIR/core/scripts/post-issue-comment.sh <iid> "comment"`
### 3. Assign Issue to Team Member
When user asks to assign an issue:
1. Run: `bash $PLUGIN_DIR/core/scripts/list-project-members.sh` to find user ID
2. Run: `bash $PLUGIN_DIR/core/scripts/update-issue.sh <iid> --assignee-ids "<user_id>"`
### 4. Create Issue with Assignment
When user asks to create and assign an issue:
1. Run: `bash $PLUGIN_DIR/core/scripts/list-project-members.sh` to find user ID
2. Run: `bash $PLUGIN_DIR/core/scripts/list-milestones.sh` to find milestone ID (if needed)
3. Run: `bash $PLUGIN_DIR/core/scripts/create-issue.sh '{"title": "...", "assignee_ids": [<user_id>], "milestone_id": <milestone_id>}'`
### 5. Break Down Issue into Sub-Issues
When user asks to split an issue into tasks:
1. Run: `bash $PLUGIN_DIR/core/scripts/get-issue-details.sh <parent_iid>` to understand the parent
2. For each sub-task, run: `bash $PLUGIN_DIR/core/scripts/create-sub-issue.sh <parent_iid> '{"title": "Sub-task title", "description": "..."}'`
3. Verify with: `bash $PLUGIN_DIR/core/scripts/get-issue-details.sh <parent_iid>` to see linked issues
## Output Format
Present issues as a table:
| IID | Title | State | Assignees | Labels | Milestone |
|-----|-------|-------|-----------|--------|-----------|
| #45 | Fix login timeout | opened | @alice | bug, urgent | Sprint 23 |
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.