원클릭으로
glab
Interact with GitLab using the `glab` CLI. Use for issues, merge requests, CI pipelines, and advanced API queries.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Interact with GitLab using the `glab` CLI. Use for issues, merge requests, CI pipelines, and advanced API queries.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
First-party, sovereign workflows form — author, list, and validate multi-step workflow specs (YAML, DAG of block/command/agent steps with typed I/O). Use when writing or checking .workflows/*.workflow.yaml. Execution (running workflows) is delivered by SP2; this slice provides the form (workflow_list, workflow_validate).
Conduz um experimento de dogfood onde a colônia Pi executa uma task do .project/tasks.json em dois tempos (research → código) com gates do operador. Use quando o operador quiser ativar um experimento colony-experiment-phase1 ou colony-experiment-phase2.
Use when a Pi session needs to continue local-safe work with low operator friction: discover focus, interview only for missing constraints, prepare bounded slices, use workers only behind gates, checkpoint, and stop on real risk.
Interact with web pages via browser automation: navigate, click, fill forms, screenshot, and evaluate JavaScript. Uses Chrome/Chromium remote debugging (CDP).
Operar o control-plane local-first do agents-lab com board canônico, long-runs bounded, handoff/checkpoint, rollout/rollback e espelhos externos sem perder governança.
Guia o cultivo de uma primitiva reutilizável. Use quando o usuário identificar um padrão recorrente que merece ser extraído como skill, extensão ou convenção.
| name | glab |
| description | Interact with GitLab using the `glab` CLI. Use for issues, merge requests, CI pipelines, and advanced API queries. |
Use the glab CLI to interact with GitLab. Always specify --repo namespace/project when not inside a git directory.
Provide all required fields explicitly to avoid interactive prompts:
glab mr create --title "..." --description "..." --yes
# List open issues
glab issue list --repo namespace/project
# View an issue
glab issue view 42 --repo namespace/project
# Create an issue
glab issue create --title "..." --description "..." --repo namespace/project
# Close an issue
glab issue close 42 --repo namespace/project
# List MRs
glab mr list --repo namespace/project
# View an MR
glab mr view 55 --repo namespace/project
# Create an MR (always provide title and description)
glab mr create --title "..." --description "..." --yes --repo namespace/project
# Merge an MR
glab mr merge 55 --yes --repo namespace/project
# Check MR CI status
glab mr checks 55 --repo namespace/project
# List recent pipelines
glab ci list --repo namespace/project
# View pipeline status
glab ci status --repo namespace/project
# View detailed pipeline jobs
glab ci view --repo namespace/project
# View logs for a specific job
glab ci trace --repo namespace/project
Use --output json for structured output and pipe to jq:
glab issue list --output json | jq '.[] | "\(.iid): \(.title)"'
glab mr list --output json | jq '.[] | "\(.iid) [\(.source_branch)]: \(.title)"'
# Get MR URL
glab mr view 55 --output json | jq .web_url
Use glab api for anything not covered by subcommands:
# Get project details
glab api projects/namespace%2Fproject
# List merge requests with specific fields
glab api projects/namespace%2Fproject/merge_requests --field state=opened \
| jq '.[] | "\(.iid): \(.title)"'
# Paginated results
glab api --paginate projects/namespace%2Fproject/issues | jq '.[].title'
Note: GitLab API uses URL-encoded namespace/project — replace / with %2F.