메뉴
GitLab CLI (glab) for managing GitLab resources from the command line. Use this skill when you need to work with merge requests, issues, CI/CD pipelines, projects, or any other GitLab resource. Prefer glab over raw API calls for all GitLab operations.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
C# implementation playbook for standard eBuilder library task handlers in dll/. USE FOR: implement or refactor TaskLibraryHandler classes, parse input with ParseInputParams<T>, handle transactions, choose between ConnectDataSource (write tasks) and ConnectDataSourceWithoutTransaction (readonly/query-only tasks), define query result DTOs, and shape TaskLibraryHandlerResult responses. DO NOT USE FOR: task YAML schema authoring in configs/task.*.yml, SQL YAML in configs/sql.*.yml, UI component work, or singleton-service recommendation patterns (use ebuilder-singleton-service-recommendation-patterns).
Generation playbook for mutation-* envelopes in configs/sql.*.yml. USE FOR: define mutation-level structure, inputParams, datasource and authorize, transaction isolation, response and callbacks, and orchestration strategy across steps. DO NOT USE FOR: step-level SQL step authoring details (use ebuilder-sql-step), query authoring (use ebuilder-sql-query), or symbol catalog (use ebuilder-eb-sql-symbols).
Input and validation playbook for query-* definitions in configs/sql.*.yml. USE FOR: inputParams typing, validation rules, checksBefore/checksAfter guards, and deterministic guard logic. DO NOT USE FOR: post-processing pipeline or output field shaping.
Foundation playbook for query-* definitions in configs/sql.*.yml. USE FOR: query naming, root structure, generation order, responseType selection, and minimal read-only query scaffolding. DO NOT USE FOR: deep input validation, pre/post pipeline internals, or advanced output shaping.
Post-pipeline playbook for query-* definitions in configs/sql.*.yml. USE FOR: query.<name>.post task-only result transformation, entries chaining, and baseCommand key-merge override behavior. DO NOT USE FOR: pre-step setup logic.
Pre-pipeline playbook for query-* definitions in configs/sql.*.yml. USE FOR: query.<name>.pre steps, setup/validation preload flow, jsExpression preparation, and command-omitted query behavior. DO NOT USE FOR: post-processing behavior.
| name | glab |
| description | GitLab CLI (glab) for managing GitLab resources from the command line. Use this skill when you need to work with merge requests, issues, CI/CD pipelines, projects, or any other GitLab resource. Prefer glab over raw API calls for all GitLab operations. |
glab is pre-configured and available in your environment. Use it for all
GitLab operations. Run glab <command> --help for detailed flag information.
# Issues
glab issue view <iid>
glab issue list --label "bug,priority::1"
glab issue create --title "title" --description "$(cat /tmp/desc.md)"
glab issue note <iid> -m "comment text"
# Merge requests
glab mr create --push --assignee "@me" --title "fix: title" --description "$(cat /tmp/desc.md)"
glab mr view <iid>
glab mr list --assignee <user>
glab mr update <iid> --description "$(cat /tmp/desc.md)"
# CI/CD
glab ci status
glab ci list
glab ci trace <job-id>
glab ci retry <pipeline-id>
# Machine-readable output
glab mr list --output json | jq '.[].title'
glab mr view <iid> --output json | jq '.title'
For this repository, read the GitLab remote directly from package.yml.
Use repo (or standardRepo when appropriate) as the project remote URL.
Do not run extra git remote discovery commands just to find the remote.
Templates: Check .gitlab/merge_request_templates/ and
.gitlab/issue_templates/ for project-specific templates.
References: Link issues with #123, MRs with !456, cross-project
with group/project#123.
glab api auto-prepends /api/v4/. Use relative paths:
glab api user # NOT /api/v4/user
glab api projects/:id/merge_requests
glab api projects/:id/issues | jq '.[0]'
When using -f for PUT/POST, pass simple key=value pairs. Array bracket
syntax like ids[]=1 is not supported:
glab api projects/:id/merge_requests/:iid -X PUT -f "assignee_id=1"
glab issue note, not issue comment — use -m for the message body.$(cat /tmp/file.md) for
descriptions and comments. Use a << 'EOF' heredoc (single-quoted
delimiter) when the content contains backticks or $ to prevent
shell expansion.--description "... \code` ..."` may trigger command substitution in zsh
and break the content. Prefer one of:
--description "$(cat /tmp/mr.md)" with a single-quoted heredoc source--description $'line1\nline2' when you need inline newlines\n is not a newline in normal double quotes — use ANSI-C quoting
($'...') or a file/here-doc to preserve real line breaks in MR summaries.--push on glab mr create — without it the remote branch
may not exist and MR creation fails.@me — include
--assignee "@me" on every glab mr create command.--state on mr list — use --all, --merged, or --closed.--body flag — --body is a gh flag. glab uses --description.--label to add, --unlabel to remove. Scoped labels like
status::doing auto-replace within their scope.