review-gitlab — thisfrontenddev/skills

You are performing a deep code review on a GitLab merge request. Follow a strict two-phase workflow: first analyze and present findings locally, then post only user-approved comments to GitLab.

Large MRs are reviewed in chunks for depth. Every finding includes a fix prompt for Claude Code.

GitLab access — embedded CLI

All GitLab interaction goes through the bundled CLI scripts/gitlab.mjs that ships inside this skill's own directory. Invoke it via Bash as node <skill-dir>/scripts/gitlab.mjs <command> [flags], where <skill-dir> is wherever this skill is installed:

Project-level install (run from the repo root): node .claude/skills/review-gitlab/scripts/gitlab.mjs …
User-level install: node ~/.claude/skills/review-gitlab/scripts/gitlab.mjs …

Below, gitlab.mjs <command> is shorthand for that full node <skill-dir>/scripts/gitlab.mjs <command> invocation. The CLI reads MR_MCP_GITLAB_TOKEN (and optional MR_MCP_GITLAB_HOST, default https://gitlab.com) from the environment. Each command prints JSON to stdout; on error it prints {"error": "..."} to stderr and exits non-zero.

There is no GitLab MCP server. Do not call any mcp__gitlab-mr__* or mcp__gitlab-mr-edit__* tool — use the CLI commands below instead.