glab-whatsnew
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.
Works with
--- 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. license: MIT --- # 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 ```
More Writing & Documentation skills
paper-context-resolver
lllllllama/rigorpilot-skills
Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing README guidance by default.
repo-intake-and-plan
lllllllama/rigorpilot-skills
Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.

