glab-mr-review
GitLab MR Review
Invoke explicitly with an MR URL or project and IID. Reviewing or sharing an MR URL authorizes inspection and a draft, not publication. An explicit request to post feedback authorizes publication without another confirmation. Review verdicts are recommendations; approving, merging, resolving discussions, or deleting comments requires the corresponding user instruction.
Operating modes: draft returns a local review; post publishes prepared feedback within explicit authorization; follow-up inspects existing discussions and replies to the requested findings. Resolve the intended mode and any requested focus from the user's instructions; default to draft when publishing was not requested.
1. Capture the review snapshot
Verify GitLab host, project, source/target branches, and MR identity from the URL and repository context. Use glab with the verified host/project rather than assuming the current checkout or origin owns the MR. Inspect installed command help before relying on version-specific flags.
Read MR metadata, the full diff, all commits, existing notes/discussions with pagination, and CI status. Record the current diff version's base/start/head SHAs. Fetch both relevant refs, including fork source refs when needed; compare immutable SHAs matching that diff version. If a diff is truncated or a file cannot be retrieved, obtain it separately or report incomplete coverage.
Completion: scope, snapshot, existing feedback, and unavailable evidence are recorded.
1a. Read the linked Jira ticket(s)
Find ticket keys (e.g. ABC-123) in the source branch name, MR title, description, and commit messages. For each, use the available Atlassian issue-read operation for the summary, description, acceptance criteria, and linked issues. Use the issue-comments operation separately to read recent comments. Summarize the intended behavior and use it as the contract when judging the diff: flag requirements the MR misses, behavior it adds beyond the ticket, and acceptance criteria with no test. If no ticket is found, a connector is unavailable, or access fails, record the limitation in coverage notes rather than guessing.