Working with GitLab merge requests via glab. Use when creating, updating, reviewing, or merging MRs.
npx claudepluginhub bendrucker/claudeThis skill is limited to using the following tools:
discussions.mdreview.mdscripts/diff.test.tsscripts/diff.tsscripts/discussions.test.tsscripts/discussions.tsscripts/draft-note.tsstack.mdWorking with GitLab merge requests via glab mr.
glab mr create --fill # Create from commits (push branch first!)
glab mr list # List MRs
glab mr view # View current branch's MR
glab mr checkout <id> # Check out MR branch
glab mr merge # Merge current branch's MR
Use glab mr --help and glab mr <command> --help for full options.
Always push before creating:
git push -u origin feature-branch && glab mr create --fill
Draft MRs: Use --draft to prevent accidental merges.
Auto-fill vs custom: --fill auto-populates from commits but cannot combine with --title/--description. Choose one approach.
Body from file: No --body-file flag; use --description "$(cat file.md)".
Username resolution: Flags like --reviewer and --assignee require exact usernames. Invalid names are silently ignored. Look up users first:
glab api projects/:id/members/all --paginate | jq '.[] | select(.name | test("<name>"; "i")) | {name, username}'
Prevent an MR from merging until another MR merges first. Uses the REST API directly since glab mr has no blocking subcommand.
# Block MR !10 until MR !5 merges
glab api projects/:id/merge_requests/10/blocks -X POST -f blocking_merge_request_iid=5
# List blocks on an MR
glab api projects/:id/merge_requests/10/blocks
# Remove a block
glab api projects/:id/merge_requests/10/blocks/<block-id> -X DELETE
Submit review feedback as draft notes that accumulate before publishing. See review.md for the draft notes workflow, code suggestions, and approvals.
Fetch, filter, resolve, and summarize MR discussion threads. See discussions.md for the discussions script, resolution workflow, and pagination pitfalls.
glab stack manages stacked diffs—small changes that build on each other. See stack.md.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.