agentleFS
Sign inStart free
a-ng-da-ng-d/claude-ui-color-palette/skills/gitlab-cli-skills/glab-issue/SKILL.md

glab-issue

Skill1 starsChanged 7 months agoMITView on GitHub

Create, view, update, and manage GitLab issues. Use when working with issue tracking, bug reports, feature requests, or task management. Operations include creating issues, listing with filters, viewing details, adding comments/notes, updating labels/assignees/milestones, closing/reopening, and board management. Triggers on issue, bug, task, ticket, feature request, list issues, create issue.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create, view, update, and manage GitLab issues.

    line 8
  2. Very specific:

    Use glab mr for <issue-id> to create MR that closes issue

    line 122

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

glab issue

Create, view, update, and manage GitLab issues.

Quick start

# Create an issue
glab issue create --title "Fix login bug" --label bug

# List open issues
glab issue list --state opened

# View issue details
glab issue view 123

# Add comment
glab issue note 123 -m "Working on this now"

# Close issue
glab issue close 123

Common workflows

Bug reporting workflow

  1. Create bug issue:
    glab issue create \
  --title "Login fails with 500 error" \
  --label bug \
  --label priority::high \
  --assignee @dev-lead
  2. Add reproduction steps:
    glab issue note 456 -m "Steps to reproduce:
1. Navigate to /login
2. Enter valid credentials
3. Click submit
Expected: Dashboard loads
Actual: 500 error"

Issue triage

  1. List untriaged issues:
    glab issue list --label needs-triage --state opened
  2. Update labels and assignee:
    glab issue update 789 \
  --label backend,priority::medium \
  --assignee @backend-team \
  --milestone "Sprint 23"
  3. Remove triage label:
    glab issue update 789 --unlabel needs-triage

Batch labeling:

For applying labels to multiple issues at once:

scripts/batch-label-issues.sh "priority::high" 100 101 102
scripts/batch-label-issues.sh bug 200 201 202 203

Sprint planning

View current sprint issues:

glab issue list --milestone "Sprint 23" --assignee @me

Add to sprint:

glab issue update 456 --milestone "Sprint 23"

Board view:

glab issue board view

Linking issues to work

Create MR for issue:

glab mr for 456  # Creates MR that closes issue #456

Automated workflow (create branch + draft MR):

scripts/create-mr-from-issue.sh 456 --create-mr

This automatically: creates branch from issue title → empty commit → pushes → creates draft MR.

Close via commit/MR:

git commit -m "Fix login bug

Closes #456"

Related Skills

Creating MRs from issues:

  • See glab-mr for merge request operations
  • Use glab mr for <issue-id> to create MR that closes issue
  • Script: scripts/create-mr-from-issue.sh automates branch creation + draft MR

Label management:

  • See glab-label for creating and managing labels
  • Script: scripts/batch-label-issues.sh for bulk labeling operations

Project planning:

  • See glab-milestone for release planning
  • See glab-iteration for sprint/iteration management

Command reference

For complete command documentation and all flags, see references/commands.md.

Available commands:

  • create - Create new issue
  • list - List issues with filters
  • view - Display issue details
  • note - Add comment to issue
  • update - Update title, labels, assignees, milestone
  • close - Close issue
  • reopen - Reopen closed issue
  • delete - Delete issue
  • subscribe / unsubscribe - Manage notifications
  • board - Work with issue boards

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free