agentleFS
Sign inStart free
nb-99nb-99/skillektion/skills/glab-cli/SKILL.md

glab-cli

Skill1 starsChanged 3 months agoMITView on GitHub

Operate on GitLab from the terminal with the glab CLI. Use for GitLab issues, merge requests, pipelines/CI, and releases. Mirrors the gh-cli workflow for GitLab-hosted repositories.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the glab CLI for all GitLab operations (glab api covers anything without a dedicated subcommand).

    line 8
  2. Distinctive:

    Read freely. An explicit user request that names the GitLab target and a bounded write action authorizes that action.

    line 11
  3. Distinctive:

    Always confirm immediately before destructive, irreversible, privilege-changing, or materially broader work.

    line 15
  4. Very specific:

    When linking work, reference the issue in commit footers (Refs: #123).

    line 70

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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

GitLab via the glab CLI

Use the glab CLI for all GitLab operations (glab api covers anything without a dedicated subcommand). Prerequisite: glab auth status must be authenticated.

Read freely. An explicit user request that names the GitLab target and a bounded write action authorizes that action. Otherwise, show the exact mutation and ask for confirmation before running it.

Always confirm immediately before destructive, irreversible, privilege-changing, or materially broader work. This includes merges, closing or deleting content, publishing or deleting releases, changing access or secrets, and any action whose effects exceed the request. Recheck the project and object identifier before every mutation.

Repos & info

glab repo view GROUP/PROJECT
glab api projects/GROUP%2FPROJECT          # URL-encode the slash as %2F

Issues

glab issue list --repo GROUP/PROJECT
glab issue view NUMBER --comments
glab issue create --title T --description D   # WRITE
glab issue note NUMBER --message M            # WRITE

Merge requests

glab mr list
glab mr view NUMBER --comments
glab mr diff NUMBER
glab mr create --source-branch BRANCH --target-branch main --title T   # WRITE
glab mr approve NUMBER                                                 # WRITE
glab mr merge NUMBER --squash                                          # HIGH-RISK: confirm

Pipelines / CI

glab ci list
glab ci view              # current branch's pipeline
glab ci status
glab ci trace JOB_ID      # stream a job's log
glab ci retry JOB_ID      # HIGH-RISK: confirm

Releases

glab release list
glab release view TAG
glab release create TAG --notes N   # HIGH-RISK: confirm

Tips

  • -R GROUP/PROJECT (or --repo) targets a project from anywhere.
  • glab api --paginate <endpoint> for raw REST access and pagination.
  • When linking work, reference the issue in commit footers (Refs: #123).

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