glab-release — Claude Code skill for GitLab releases
glab-release is a Claude Code skill that manages GitLab releases, including their notes and assets. It activates on requests about versions, tags, publishing, or release files.
MIT 129 installs ★ 51 updated 2026-10-20
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-release -a claude-codeWhat glab-release does
glab-release runs glab release commands to create, update, inspect, list, and delete GitLab releases. It can upload asset files or links and download files from a release. Use --repo to target a project other than the current one.
The skill supports JSON output for listing and viewing releases. In GitLab CI, CI_JOB_TOKEN can be used with glab's automatic login; if its permissions are insufficient, the instructions describe using a project or group access token with the api scope. It requires the glab CLI and GitLab access. Do not pass CI_JOB_TOKEN as GITLAB_TOKEN, since the Releases API rejects that credential in the PRIVATE-TOKEN header. Uploads may exist even if release creation fails, so the release and its assets need verification before a retry.
What it helps with
- create or update a release for a Git tag
- inspect release history and version details
- attach files or links to a GitLab release
- download files from a release
- delete a release by tag
Example prompts for the agent
- Create a GitLab release for tag
v1.2.0using notes fromCHANGELOG.md. - List this project's releases as JSON.
- Download the assets from the latest GitLab release.
How to install glab-release
1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-release -a claude-code2Manually: put the files in place
~/.claude/skills/glab-release/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/glab-release/
1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-release -a codex2Manually: put the files in place
.agents/skills/glab-release/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-release -a cursor2Manually: put the files in place
.cursor/skills/glab-release/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install vince-winkintel/gitlab-cli-skills glab-release2Manually: put the files in place
.github/skills/glab-release/SKILL.md1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-release -a gemini-cli2Platform CLI
gemini skills install https://github.com/vince-winkintel/gitlab-cli-skills --path glab-releaseManually: put the files in place
.devin/skills/glab-release/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-release -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about glab-release
How do I install glab-release in Claude Code?
Run npx skills add vince-winkintel/gitlab-cli-skills --skill glab-release -a claude-code. The skill file is installed at ~/.claude/skills/glab-release/SKILL.md.
What does glab-release do?
It manages GitLab releases through glab release: creating or updating them, listing and viewing release details, handling assets, and deleting releases.
What does glab-release need in GitLab CI?
It needs the glab CLI and GitLab access. CI can use CI_JOB_TOKEN with glab's automatic login; when that token lacks access, the instructions describe a project or group token with the api scope.
Source text
SKILL.md · MIT
---
name: glab-release
description: Manage GitLab releases including create, list, view, delete, download, and upload release assets. Use when publishing software versions, managing release notes, uploading binaries/artifacts, downloading release files, or viewing release history. Triggers on release, version, tag, publish release, release notes, download release.
---
# glab release
> Capture key `685c1cbd7`: checksum-verified macOS arm64 binary, source commit `685c1cbd74c882e0c93d7011657adde811582ed7`; archive SHA-256 `e77f5756c3c8d9ffeaef0bf234533f395680ab9f128a75cec4c1bd7a1049788c`. Only fences marked `685c1cbd7` use this capture. Normalization removes trailing spaces/tabs only; indentation, blank lines, wrapping, truncation, and product spelling (including `Gitlab`) are preserved. Other fences retain their individual prior provenance.
## Asset-link validation and creation
`release create` and `release upload` reject null elements such as `[null]` in `--assets-links` before sending requests, reporting the zero-based index. Supply a JSON array of link objects with the intended names, URLs, optional `link_type`, and `direct_asset_path`. Do not combine deprecated `filepath` with `direct_asset_path`; the former alone is aliased with a warning.
For a new release, asset links are sent in the release-creation request, including links for files uploaded beforehand. This makes the release visible with its links immediately; it does not make the entire operation one network request or transactional. File/package uploads can already exist when release creation fails. Updating an existing release and `release upload` still create links separately. Verify existing release/assets before retrying after partial failure.
Creation, upload, update, deletion, tag creation, and milestone closure are operational writes. Obtain approval for the exact project, tag, release notes, asset destinations, and side effects; verify host/actor before execution. `release create` can update an existing release; use `--no-update` when that must be refused.
## List totals and pagination
`glab release list` uses the API-reported total in its text header when available, separate from the number of returned rows. Missing totals must not be treated as proof there are no other pages. JSON contains the requested page's items, not every item counted by the header. Use `--page` and `--per-page` to traverse results explicitly; do not equate JSON array length with the server total.
## Asset transport
Release downloads recognize same-instance Markdown upload asset URLs and fetch them through the authenticated API, including project-ID and namespace/project upload paths. Use the intended host and identity; do not work around an authentication failure by exposing tokens in URLs. Asset uploads can run in parallel, so verify the final release assets instead of depending on upload completion order.
## Overview
<!-- help-capture: 685c1cbd7:a8ea3498e523 -->
```text
A release bundles a Git tag with release notes and downloadable
assets, such as binaries or source archives.
Create and update releases, list and view them, upload assets, and
download or delete releases. Use `--repo` to target a project other
than the current one.
USAGE
glab release <command> [command] [--flags]
COMMANDS
create <tag> [<files>...] [--flags] Create a new GitLab release, or update an existing one.
delete <tag> [--flags] Delete a GitLab release.
download [<tag>] [--flags] Download asset files from a GitLab release.
list [--flags] List releases in a repository.
upload <tag> [<files>...] [--flags] Upload release asset files or links to a GitLab release.
view [<tag>] [--flags] View information about a GitLab release.
FLAGS
-h --help Show help for this command.
-R --repo Select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted.
```
## Quick start
```bash
glab release --help
```
## Structured output
`glab release list` and `glab release view` support `--output json` / `-F json` for structured output, which is useful for agent automation.
`--notes` and `--notes-file` are optional for `glab release create`, including when it updates an existing release.
The tag is optional for `glab release view` and `glab release download`; omit it to target the latest release. Pass an explicit tag in release automation when reproducibility matters.
```bash
# List releases with JSON output
glab release list --output json
glab release list -F json
# View a release with JSON output
glab release view v1.2.0 --output json
glab release view v1.2.0 -F json
# Create a release without notes
glab release create v1.2.0
# Update a release without notes
glab release create v1.2.0 --name "My Release"
```
## Creating releases in GitLab CI/CD
For a pipeline job, prefer the predefined `CI_JOB_TOKEN` with glab CI auto-login; see [glab-auth](../glab-auth/SKILL.md) for the general mechanism and environment-variable precedence. The Releases API accepts that credential in the `JOB-TOKEN` header:
```bash
GLAB_ENABLE_CI_AUTOLOGIN=true \
glab release create "$CI_COMMIT_TAG" \
--notes-file CHANGELOG.md \
--ref "$CI_COMMIT_SHA"
```
Do not assign `CI_JOB_TOKEN` to `GITLAB_TOKEN`: glab sends `GITLAB_TOKEN` as `PRIVATE-TOKEN`, which the Releases API rejects for a job token and can surface as `404 Not Found`. When job-token access is insufficient, use an approved project or group access token with `api` scope through `GITLAB_TOKEN`; never print that token.
## Subcommands
See [references/commands.md](references/commands.md) for full `--help` output.
© vince-winkintel · MIT · vince-winkintel/gitlab-cli-skills