agentleFS
a-ng-da-ng-d/claude-ui-color-palette/skills/gitlab-cli-skills/glab-workitems/SKILL.md

glab-workitems

Skill1 starsChanged 7 months agoMITView on GitHub

List and manage GitLab work items (tasks, OKRs, key results, epics). Use when working with GitLab's work item types beyond standard issues. Triggers on work items, tasks, OKRs, key results, epic list, workitems list.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Very specific:

    Use glab issue for standard issue workflows.

    line 81
  2. Distinctive:

    Check the GitLab UI under the project's "Plan > Work Items" sidebar.

    line 90
  3. Distinctive:

    Not all work item types are enabled on every GitLab instance.

    line 93

≈ “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 workitems

List and manage GitLab work items — the next-generation work tracking format in GitLab that supports tasks, OKRs, key results, epics, and more.

Added in glab v1.87.0

What Are Work Items?

Work items are GitLab's unified work tracking model. They extend beyond traditional issues to support:

  • Tasks — sub-tasks within an issue
  • OKRs — Objectives and Key Results
  • Key Results — measurable outcomes linked to OKRs
  • Epics (next-gen) — large bodies of work across milestones
  • Incidents — linked to incident management

Quick Start

# List work items in current project
glab workitems list

# List in a specific project
glab workitems list --repo owner/project

# Output as JSON
glab workitems list --output json

Common Workflows

List Work Items

# All work items (default: open)
glab workitems list

# Filter by type
glab workitems list --type Task
glab workitems list --type OKR
glab workitems list --type KeyResult
glab workitems list --type Epic

# Filter by state
glab workitems list --state opened
glab workitems list --state closed

# JSON for scripting
glab workitems list --output json | python3 -c "
import sys, json
items = json.load(sys.stdin)
for item in items:
    print(f\"{item['iid']}: {item['title']} [{item['type']}]\")
"

Use with a Specific Repo or Group

# Specific repo
glab workitems list --repo mygroup/myproject

# Group-level work items
glab workitems list --group mygroup

Work Items vs Issues

FeatureIssuesWork Items
Standard bug/feature tracking✅✅
Tasks (sub-tasks)❌✅
OKRs / Key Results❌✅
Next-gen Epics❌✅
CLI supportFulllist (v1.87.0)

Use glab issue for standard issue workflows. Use glab workitems when working with tasks, OKRs, or next-gen epics.

Troubleshooting

"workitems: command not found":

  • Requires glab v1.87.0+. Check with glab version.

Empty results when you expect items:

  • Work items are a separate type from issues. Items created as issues won't appear here unless they've been converted.
  • Check the GitLab UI under the project's "Plan > Work Items" sidebar.

Type filter returns nothing:

  • Not all work item types are enabled on every GitLab instance. GitLab SaaS has broader support than self-managed instances.

Related Skills

  • glab-issue — Standard issue management
  • glab-milestone — Milestones (often used with OKRs)
  • glab-iteration — Sprint/iteration management
  • glab-incident — Incident management (a work item type)

Command Reference

glab workitems list [--flags]

Flags:
  --group        Select a group/subgroup
  --output       Format output as: text, json
  --page         Page number
  --per-page     Number of items per page
  --repo         Select a repository
  --state        Filter by state: opened, closed, all
  --type         Filter by work item type
  -h, --help     Show help

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.