glab-whatsnew — Claude Code skill: release notes and install
This Claude Code skill displays GitLab CLI release notes through glab whatsnew. It activates for questions about new releases, changes after an upgrade, or notes from a chosen version.
MIT 112 installs ★ 51 updated 2026-10-20
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-whatsnew -a claude-codeWhat glab-whatsnew does
The skill runs glab whatsnew to display GitLab CLI release notes. With no arguments, the command shows releases since the last visit or post-upgrade banner; implicit history is limited to the latest 10 releases.
Pass a version to inspect one release, use --latest for the newest one, or set --since <version> for an explicit starting point. After reviewing changes, the skill suggests checking affected commands with glab <command> --help before editing instructions. The glab command must be installed.
What it helps with
- see what changed after upgrading
glab - read notes for a specific GitLab CLI release
- review releases newer than a chosen version
- check command changes before updating instructions
Example prompts for the agent
- Show what changed in GitLab CLI since my upgrade.
- Display the release notes for
v1.102.0. - Show
glabreleases newer thanv1.100.0.
How to install glab-whatsnew
1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-whatsnew -a claude-code2Manually: put the files in place
~/.claude/skills/glab-whatsnew/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/glab-whatsnew/
1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-whatsnew -a codex2Manually: put the files in place
.agents/skills/glab-whatsnew/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-whatsnew -a cursor2Manually: put the files in place
.cursor/skills/glab-whatsnew/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install vince-winkintel/gitlab-cli-skills glab-whatsnew2Manually: put the files in place
.github/skills/glab-whatsnew/SKILL.md1Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-whatsnew -a gemini-cli2Platform CLI
gemini skills install https://github.com/vince-winkintel/gitlab-cli-skills --path glab-whatsnewManually: put the files in place
.devin/skills/glab-whatsnew/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-whatsnew -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-whatsnew
How do I install glab-whatsnew in Claude Code?
Run npx skills add vince-winkintel/gitlab-cli-skills --skill glab-whatsnew -a claude-code. The skill file is at ~/.claude/skills/glab-whatsnew/SKILL.md.
What does glab-whatsnew do?
It displays GitLab CLI release notes since the last visit, for a selected version, or from a specified baseline.
What does glab-whatsnew need to run?
The glab command must be installed; the skill calls it to retrieve release notes.
Source text
SKILL.md · MIT
--- name: glab-whatsnew description: View GitLab CLI release notes with glab whatsnew. Use when checking what changed after upgrading glab, reviewing release notes since a baseline version, or asking what's new in the GitLab CLI. Triggers on whatsnew, what's new, release notes, glab upgrade notes, glab changelog since. --- # glab whatsnew View GitLab CLI release notes from the terminal. ## Quick start ```bash # Show release notes since the last viewed/post-upgrade baseline, capped at 10 releases glab whatsnew # Show notes for the latest published release glab whatsnew --latest # Show notes for a specific release glab whatsnew v1.102.0 # Show notes for every release after a baseline glab whatsnew --since v1.100.0 ``` ## When to use Use `glab whatsnew` after upgrading `glab` or before updating automation that depends on command behavior. It is the quickest CLI-native path for inspecting upstream release notes without opening a browser. ## Behavior notes - With no arguments, `glab whatsnew` shows releases published since the last time you ran `whatsnew` or saw the post-upgrade banner. - The implicit history is capped at the most recent 10 releases. - Use `--since <version>` for deterministic automation or review work where you need an explicit baseline. - Use `--latest` when you only care about the latest published release. ## Agent workflow ```bash # Review all releases newer than the skill repo's last processed glab baseline glab whatsnew --since v1.100.0 # Then inspect command help for any relevant new/changed command surfaces glab repo prune --help glab mr note create --help glab stack sync --help ``` Do not treat release-note prose alone as a contract. For skill updates, verify changed command surfaces with `glab <command> --help` or upstream docs/source before editing guidance. ## Command reference ```text glab whatsnew [version] [--flags] Flags: --latest Show release notes for the latest published release only --since Show release notes for every release newer than this version -h --help Show help for this command ```
© vince-winkintel · MIT · vince-winkintel/gitlab-cli-skills