mr-reviewlisted

# GitLab Code Review Skill Reviews a GitLab MR using the `glab` CLI: fetch the diff and prior comments, optionally pull issue context, analyze, then post findings as an MR note. **Requirements** - `bash` tool access - Either the `glab` CLI (authenticated against the company's self-hosted GitLab), or `curl` + `jq` — see the **API fallback** appendix at the end of this file **Command compatibility.** This skill sticks to long-stable `glab` commands. Avoid `glab mr note list` and `glab mr note create` — the first is marked experimental and may be removed; both are absent from older glab versions still widely installed. Use `glab mr view --comments` and `glab mr note -m` instead. **Never type `<MR_ID>` into a shell.** Bash reads `<` as input redirection, so `glab mr view <MR_ID>` tries to open a file named `MR_ID`, fails with a misleading error, and never runs glab at all. Bind the inputs to variables once (Step 0) and use `"$MR_ID"` everywhere after. --- ## Step 0 — Verify tooling, auth & collect inputs Two distinct failures live here — don't conflate them: ```bash command -v glab || echo "NO_GLAB" ``` **If glab is missing**, don't stop and don't improvise — skip to the **API fallback** appendix at the end of this file and carry on with the same review steps. Everything `glab` does here is a thin wrapper over the GitLab REST API, so nothing about the review itself changes. **If glab exists**, check auth separately: ```bash glab auth status ``` If auth fails, **do n