gitlab-clilisted

# GitLab CLI Skill Use the instance and rules below when constructing all glab commands. ## Configuration Set your GitLab hostname below before using this skill: | Setting | Value | |---|---| | GitLab Hostname | `<YOUR_GITLAB_HOSTNAME>` (e.g. `gitlab.example.com`) | Replace `<YOUR_GITLAB_HOSTNAME>` with your GitLab instance hostname throughout this skill. ### Prerequisites (one-time setup by user) If not already authenticated, inform the user that authentication is required and ask them to complete the following steps manually. Do not perform these steps yourself. 1. Install the `glab` CLI if not already installed: ```bash brew install glab ``` 2. Run the following command to authenticate with your GitLab instance: ```bash glab auth login --hostname <YOUR_GITLAB_HOSTNAME> ``` ## MR Code Review When asked to review a GitLab MR or PR (URL or MR ID provided), extract the `<group/repo>` and `<MR_ID>` from the URL (ask the user if the repo is missing), then use `glab api --hostname <YOUR_GITLAB_HOSTNAME>` to fetch the MR metadata (`projects/<URL_ENCODED_REPO>/merge_requests/<MR_ID>`) and its diff (`…/diffs --paginate`), where the repo path is URL-encoded with `/` → `%2F`. To fully understand the context and impact of all code changes, read the complete source branch codebase — the diff alone does not capture the surrounding logic, dependencies, or broader design that the changes interact with. Report the MR title, author, and branches, then review all changed files fo